mTLS client verification is skipped in fs2 on Node.js
fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-31183
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 05:43 UTC · Revision 1
Source evidence
mTLS client verification is skipped in fs2 on Node.js
core-osv · Original sourcePublished 1 Aug 2022, 19:50 UTC
fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.
osv:CVE-2022-31183
Complete source record
{
"id": "a3f402be2d72dd7bb6a82b05893e3a5acbed2130ea0fbf435d1bedeacd0553e5",
"url": "https://osv.dev/vulnerability/CVE-2022-31183",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "mTLS client verification is skipped in fs2 on Node.js",
"summary": "fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.",
"evidence": "osv:CVE-2022-31183",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2022-31183",
"aliases": [
"CVE-2022-31183",
"GHSA-2cpx-6pqp-wf35"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/typelevel/fs2",
"type": "GIT",
"events": [
{
"introduced": "ad9cea3f0d9e15f2648d02b76615767fe60e1511"
},
{
"fixed": "47bced431dcad2aa2efb5f60493b26a3aa05ca7e"
},
{
"fixed": "659824395826a314e0a4331535dbf1ef8bef8207"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:typelevel:fs2:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.1.0"
},
{
"fixed": "3.2.11"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "659824395826a314e0a4331535dbf1ef8bef8207"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v3.2.9",
"v3.2.10",
"v3.2.8",
"v3.2.7",
"v3.2.6",
"v3.2.5",
"v3.2.4",
"v3.2.3",
"v3.2.2",
"v3.2.1",
"v3.2.0",
"v3.1.6",
"v3.1.5",
"v3.1.4",
"v3.1.2",
"v3.1.1",
"v3.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-31183.json"
}
}
],
"modified": "2026-10-28T02:30:43.178768882Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/31xxx/CVE-2022-31183.json",
"https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35",
"https://nvd.nist.gov/vuln/detail/CVE-2022-31183",
"https://github.com/nodejs/node/issues/43994",
"https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207"
],
"provider_metadata": {
"cwe_ids": [
"CWE-295"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/31xxx/CVE-2022-31183.json"
}
},
"related_cves": [
{
"value": "CVE-2022-31183",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 510799,
"published_at": "2022-08-01T19:50:11+00:00"
}