When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs…
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 16.20.1, 18.16.1, 20.3.1 and 14 more.
When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| nodejs | node.js | >=16.0.0 <16.20.1, >=18.0.0 <18.16.1, >=20.0.0 <20.3.1 | 16.20.1, 18.16.1, 20.3.1 |
| nodejs | >=10.0 <10.*, >=11.0 <11.*, >=12.0 <12.*, >=13.0 <13.*, >=14.0 <14.*, >=15.0 <15.*, >=16.0 <16.20.1, >=17.0 <17.*, >=18.0 <18.16.1, >=19.0 <19.*, >=20.0 <20.3.1, >=4.0 <4.*, >=5.0 <5.*, >=6.0 <6.*, >=7.0 <7.*, >=8.0 <8.*, >=9.0 <9.* | 10.*, 11.*, 12.*, 13.*, 14.*, 15.*, 16.20.1, 17.*, 18.16.1, 19.*, 20.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