{"api_version":"1","generated_at":"2026-07-23T12:52:44+00:00","cve":"CVE-2022-31183","urls":{"html":"https://cve.report/CVE-2022-31183","api":"https://cve.report/api/cve/CVE-2022-31183.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2022-31183","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-31183"},"summary":{"title":"CVE-2022-31183","description":"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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2022-08-01 20:15:00","updated_at":"2022-08-09 19:38:00"},"problem_types":["CWE-295"],"metrics":[],"references":[{"url":"https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35","name":"https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35","refsource":"CONFIRM","tags":[],"title":"mTLS client verification is skipped in Node.js TLS server · Advisory · typelevel/fs2 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/nodejs/node/issues/43994","name":"https://github.com/nodejs/node/issues/43994","refsource":"MISC","tags":[],"title":"How to use `new tls.TLSSocket(...)` to establish a secure connection? · Issue #43994 · nodejs/node · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207","name":"https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207","refsource":"MISC","tags":[],"title":"First attempt at test for GHSA-2cpx-6pqp-wf35 · typelevel/fs2@6598243 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-31183","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31183","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2022","cve_id":"31183","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"typelevel","cpe5":"fs2","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2022-31183","STATE":"PUBLIC","TITLE":"mTLS client verification is skipped in fs2 on Node.js"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"fs2","version":{"version_data":[{"version_value":">= 3.1.0, < 3.2.11"}]}}]},"vendor_name":"typelevel"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-295: Improper Certificate Validation"}]}]},"references":{"reference_data":[{"name":"https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35","refsource":"CONFIRM","url":"https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35"},{"name":"https://github.com/nodejs/node/issues/43994","refsource":"MISC","url":"https://github.com/nodejs/node/issues/43994"},{"name":"https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207","refsource":"MISC","url":"https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207"}]},"source":{"advisory":"GHSA-2cpx-6pqp-wf35","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2022-08-01 20:15:00","lastModifiedDate":"2022-08-09 19:38:00","problem_types":["CWE-295"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL"},"exploitabilityScore":3.9,"impactScore":5.9}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:typelevel:fs2:*:*:*:*:*:*:*:*","versionStartIncluding":"3.1.0","versionEndExcluding":"3.2.11","cpe_name":[]}]}]}},"legacy_mitre":{"record":null,"notes":[]}}}