CVE-2022-31183

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

• https://github.com/nodejs/node/issues/43994
• https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/

For more information

If you have any questions or comments about this advisory:

• Open an issue.
• Contact the Typelevel Security Team.

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.

CVE-2022-31183 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.11); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2022-31183? CVE-2022-31183 is a critical-severity security vulnerability in co.fs2:fs2-io (maven), affecting versions >= 3.1.0, < 3.2.11. It is fixed in 3.2.11.
2. How severe is CVE-2022-31183? CVE-2022-31183 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-31183?
   • co.fs2:fs2-io (maven) (versions >= 3.1.0, < 3.2.11)
   • co.fs2:fs2-io_2.12 (maven) (versions >= 3.1.0, < 3.2.11)
   • co.fs2:fs2-io_3 (maven) (versions >= 3.1.0, < 3.2.11)
   • co.fs2:fs2-io_2.13 (maven) (versions >= 3.1.0, < 3.2.11)
   • co.fs2:fs2-io_sjs1_2.13 (maven) (versions >= 3.1.0, < 3.2.11)
   • co.fs2:fs2-io_sjs1_3 (maven) (versions >= 3.1.0, < 3.2.11)
4. Is there a fix for CVE-2022-31183? Yes. CVE-2022-31183 is fixed in 3.2.11. Upgrade to this version or later.
5. Is CVE-2022-31183 exploitable, and should I be worried? Whether CVE-2022-31183 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31183 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31183?
   • Upgrade co.fs2:fs2-io to 3.2.11 or later
   • Upgrade co.fs2:fs2-io_2.12 to 3.2.11 or later
   • Upgrade co.fs2:fs2-io_3 to 3.2.11 or later
   • Upgrade co.fs2:fs2-io_2.13 to 3.2.11 or later
   • Upgrade co.fs2:fs2-io_sjs1_2.13 to 3.2.11 or later
   • Upgrade co.fs2:fs2-io_sjs1_3 to 3.2.11 or later