Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly.

Summary

Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

Timeline

1. Feb 24, 2022, 6:27 PM UTCCVE published
2. Oct 8, 2026, 9:15 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Oct 8, 2026, 9:24 PM UTCRecord last updated

Affected versions

• NodeJS Node

  From 4.0 · fixed in 4.*; From 5.0 · fixed in 5.*; From 6.0 · fixed in 6.*; From 7.0 · fixed in 7.*; From 8.0 · fixed in 8.*; From 9.0 · fixed in 9.*; From 10.0 · fixed in 10.*; From 11.0 · fixed in 11.*; From 12.0 · fixed in 12.22.9; From 13.0 · fixed in 13.*; From 14.0 · fixed in 14.18.3; From 15.0 · fixed in 15.*; From 16.0 · fixed in 16.13.2; From 17.0 · fixed in 17.3.1

• nodeBitnami

  fixed in 12.22.9; From 14.0.0 · fixed in 14.18.3; From 16.0.0 · fixed in 16.13.2; From 17.0.0 · fixed in 17.3.1

• node-minBitnami

  fixed in 12.22.9; From 14.0.0 · fixed in 14.18.3; From 16.0.0 · fixed in 16.13.2; From 17.0.0 · fixed in 17.3.1

References 6