Description
Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
NodeJS Node
Default version status: unaffected
4.0 to < 4.*affected5.0 to < 5.*affected6.0 to < 6.*affected7.0 to < 7.*affected8.0 to < 8.*affected9.0 to < 9.*affected10.0 to < 10.*affected11.0 to < 11.*affected12.0 to < 12.22.9affected13.0 to < 13.*affected14.0 to < 14.18.3affected15.0 to < 15.*affected16.0 to < 16.13.2affected17.0 to < 17.3.1affected
References
- https://hackerone.com/reports/1429694 ↗
- https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/ ↗
- https://www.oracle.com/security-alerts/cpuapr2022.html ↗
- https://security.netapp.com/advisory/ntap-20220325-0007/ ↗
- https://www.debian.org/security/2022/dsa-5170 ↗
- https://www.oracle.com/security-alerts/cpujul2022.html ↗