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.
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 9%. Fixed in 10.*, 11.*, 12.22.9 and 11 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| nodejs | >=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, >=4.0 <4.*, >=5.0 <5.*, >=6.0 <6.*, >=7.0 <7.*, >=8.0 <8.*, >=9.0 <9.* | 10.*, 11.*, 12.22.9, 13.*, 14.18.3, 15.*, 16.13.2, 17.3.1, 4.*, 5.*, 6.*, 7.*, 8.*, 9.* |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket