Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| NodeJS | Node | >= 4.0, < 4.*; >= 5.0, < 5.*; >= 6.0, < 6.*; >= 7.0, < 7.*; >= 8.0, < 8.*; >= 9.0, < 9.*; >= 10.0, < 10.*; >= 11.0, < 11.*; >= 12.0, < 12.22.9; >= 13.0, < 13.*; >= 14.0, < 14.18.3; >= 15.0, < 15.*; >= 16.0, < 16.13.2; >= 17.0, < 17.3.1 |
References
- https://hackerone.com/reports/1429694Exploit, Mitigation, Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/Release Notes, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220325-0007/Third Party Advisory
- https://www.debian.org/security/2022/dsa-5170Third Party Advisory
- https://www.oracle.com/security-alerts/cpuapr2022.htmlPatch, Third Party Advisory
- https://www.oracle.com/security-alerts/cpujul2022.htmlThird Party Advisory
- https://hackerone.com/reports/1429694Exploit, Mitigation, Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/Release Notes, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220325-0007/Third Party Advisory
- https://www.debian.org/security/2022/dsa-5170Third Party Advisory
- https://www.oracle.com/security-alerts/cpuapr2022.htmlPatch, Third Party Advisory
- https://www.oracle.com/security-alerts/cpujul2022.htmlThird Party Advisory
Timeline
- Published
- Feb 24, 2022
- Last modified
- Oct 8, 2026
- NVD status
- Modified