mTLS client verification is skipped in fs2 on Node.js
typelevel fs2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| co.fs2:fs2-io Maven |
|
|
| co.fs2:fs2-io_2.12 Maven |
|
|
| co.fs2:fs2-io_3 Maven |
typelevel fs2
| Product | Affected | Fixed in |
|---|---|---|
| co.fs2:fs2-io Maven |
|
|
| co.fs2:fs2-io_2.12 Maven |
|
|
| co.fs2:fs2-io_3 Maven |
≥ 3.1.0 · < 3.2.11
|
| co.fs2:fs2-io_2.13 Maven |
|
|
| co.fs2:fs2-io_sjs1_2.13 Maven |
|
|
| co.fs2:fs2-io_sjs1_3 Maven |
|
|
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.
From the CVE record · GitHub_M
On Node.js, fs2-io server-mode TLSSockets ignore `requestCert = true` and skip peer certificate verification. A network attacker without a valid client certificate can establish a connection intended to require mTLS; no user interaction is needed. JVM TLS and client-mode TLSSockets are not affected.
Check applications using Maven `co.fs2:fs2-io`, `fs2-io_2.12`, `fs2-io_3`, `fs2-io_2.13`, `fs2-io_sjs1_2.13`, or `fs2-io_sjs1_3` versions >=3.1.0 and <3.2.11 on Node.js.