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:
fs2-io
running on Node.js. The JVM TLS implementation is completely independent.
TLSSocket
s in server-mode. Client-mode TLSSocket
s are implemented via a different API.
- 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 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:
Impact
When establishing a server-mode
TLSSocket
usingfs2-io
on Node.js, the parameterrequestCert = true
is ignored, peer certificate verification is skipped, and the connection proceeds.The vulnerability is limited to:
fs2-io
running on Node.js. The JVM TLS implementation is completely independent.TLSSocket
s in server-mode. Client-modeTLSSocket
s are implemented via a different API.requestCert = true
inTLSParameters
. The default setting isfalse
for server-modeTLSSocket
s.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, aSSLException
is raised.Workarounds
If using an unpatched version on Node.js, do not use a server-mode
TLSSocket
withrequestCert = true
to establish a mTLS connection.References
For more information
If you have any questions or comments about this advisory: