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.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Node.js | Nodejs | 16.0.0 (including) | 16.20.1 (excluding) |
Node.js | Nodejs | 18.0.0 (including) | 18.16.1 (excluding) |
Node.js | Nodejs | 20.0.0 (including) | 20.3.1 (excluding) |
Red Hat Enterprise Linux 8 | RedHat | nodejs:18-8080020230718130356.63b34585 | * |
Red Hat Enterprise Linux 8 | RedHat | nodejs:16-8080020230718141521.63b34585 | * |
Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | nodejs:16-8060020230906023909.ad008a3a | * |
Red Hat Enterprise Linux 9 | RedHat | nodejs:18-9020020230717125503.rhel9 | * |
Red Hat Enterprise Linux 9 | RedHat | nodejs-1:16.20.1-1.el9_2 | * |
Red Hat Enterprise Linux 9.0 Extended Update Support | RedHat | nodejs-1:16.20.2-1.el9_0 | * |
Nodejs | Ubuntu | bionic | * |
Nodejs | Ubuntu | kinetic | * |
Nodejs | Ubuntu | lunar | * |
Nodejs | Ubuntu | mantic | * |
Nodejs | Ubuntu | trusty | * |
Nodejs | Ubuntu | xenial | * |