cve.bz

CVE-2022-31183 typelevel fs2: Improper Certificate Validation

9.8 criticalExploit referenceEPSS 0.8%Fix available

Critical (9.8) in typelevel fs2. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in co.fs2:fs2-io 3.2.11.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-31183 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-31183?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-31183?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-31183 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
typelevel:fs2from 3.1.0 before 3.2.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io>=3.1.0 <3.2.113.2.11
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io_2.12>=3.1.0 <3.2.113.2.11
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io_3>=3.1.0 <3.2.113.2.11
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io_2.13>=3.1.0 <3.2.113.2.11
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io_sjs1_2.13>=3.1.0 <3.2.113.2.11
GHSA-2cpx-6pqp-wf35Mavenco.fs2:fs2-io_sjs1_3>=3.1.0 <3.2.113.2.11

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON