Skip to content

fs2-io skips mTLS client verification

Critical severity GitHub Reviewed Published Jul 26, 2022 in typelevel/fs2 • Updated Sep 30, 2025

Package

maven co.fs2:fs2-io (Maven)

Affected versions

>= 3.1.0, < 3.2.11

Patched versions

3.2.11
maven co.fs2:fs2-io_2.12 (Maven)
>= 3.1.0, < 3.2.11
3.2.11
maven co.fs2:fs2-io_2.13 (Maven)
>= 3.1.0, < 3.2.11
3.2.11
maven co.fs2:fs2-io_3 (Maven)
>= 3.1.0, < 3.2.11
3.2.11
maven co.fs2:fs2-io_sjs1_2.13 (Maven)
>= 3.1.0, < 3.2.11
3.2.11
maven co.fs2:fs2-io_sjs1_3 (Maven)
>= 3.1.0, < 3.2.11
3.2.11

Description

Impact

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. TLSSockets in server-mode. Client-mode TLSSockets are implemented via a different API.
  3. mTLS as enabled via requestCert = true in TLSParameters. The default setting is false for server-mode TLSSockets.

It was introduced with the initial Node.js implementation of fs2-io in v3.1.0.

Patches

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.

Workarounds

If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.

References

For more information

If you have any questions or comments about this advisory:

References

@ChristopherDavenport ChristopherDavenport published to typelevel/fs2 Jul 26, 2022
Published to the GitHub Advisory Database Jul 29, 2022
Reviewed Jul 29, 2022
Published by the National Vulnerability Database Aug 1, 2022
Last updated Sep 30, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(42nd percentile)

Weaknesses

Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate. Learn more on MITRE.

CVE ID

CVE-2022-31183

GHSA ID

GHSA-2cpx-6pqp-wf35

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.