CVE-2022-31183
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 9.1 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Weakness
- CWE-295 · Improper certificate validation
- Record status
- Modified
Affected
- Typelevel fs2 < 3.2.11
Attack profile CVSS 3.1 · 9.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-31183.md and follow it. Check whether this project is affected by CVE-2022-31183. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207
- https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35
- https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207
- https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35
References
- https://github.com/nodejs/node/issues/43994
- https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207
- https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35
- https://github.com/nodejs/node/issues/43994
- https://github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207
- https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35