Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the –security-revert command-line option.
The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate, resulting in incorrect trust of any resource that is associated with that certificate.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Node.js | Nodejs | * | 12.22.9 (excluding) |
| Node.js | Nodejs | 14.0.0 (including) | 14.18.3 (excluding) |
| Node.js | Nodejs | 16.0.0 (including) | 16.13.2 (excluding) |
| Node.js | Nodejs | 17.0.0 (including) | 17.3.1 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:12-8060020220523160029.ad008a3a | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:14-8070020221020110846.bd1311ed | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:16-8070020221207164159.bd1311ed | * |
| Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions | RedHat | nodejs:12-8010020220518102644.c27ad7f8 | * |
| Red Hat Enterprise Linux 8.2 Extended Update Support | RedHat | nodejs:12-8020020220523154454.4cda2c84 | * |
| Red Hat Enterprise Linux 8.4 Extended Update Support | RedHat | nodejs:12-8040020220523155137.522a0ee4 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | nodejs:14-8060020230306170237.ad008a3a | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-nodejs12-nodejs-0:12.22.12-2.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-nodejs14-nodejs-0:14.20.1-2.el7 | * |
| RHODF-4.13-RHEL-9 | RedHat | odf4/mcg-core-rhel9:v4.13.0-41 | * |
| Nodejs | Ubuntu | bionic | * |
| Nodejs | Ubuntu | hirsute | * |
| Nodejs | Ubuntu | impish | * |
| Nodejs | Ubuntu | kinetic | * |
| Nodejs | Ubuntu | lunar | * |
| Nodejs | Ubuntu | mantic | * |
| Nodejs | Ubuntu | trusty | * |
| Nodejs | Ubuntu | trusty/esm | * |
| Nodejs | Ubuntu | xenial | * |
If a system does not follow the chain of trust of a certificate to a root server, the certificate loses all usefulness as a metric of trust. Essentially, the trust gained from a certificate is derived from a chain of trust – with a reputable trusted entity at the end of that list. The end user must trust that reputable source, and this reputable source must vouch for the resource in question through the medium of the certificate. In some cases, this trust traverses several entities who vouch for one another. The entity trusted by the end user is at one end of this trust chain, while the certificate-wielding resource is at the other end of the chain. If the user receives a certificate at the end of one of these trust chains and then proceeds to check only that the first link in the chain, no real trust has been derived, since the entire chain must be traversed back to a trusted source to verify the certificate. There are several ways in which the chain of trust might be broken, including but not limited to: