CVE-2021-44532CWE-296

CVE-2021-44532: vulnerability in NodeJS Node

Published · Updated

Follow this CVE+ Monitor Node.js+ Monitor openjdk11

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

8Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 10%
In short

Node.js had a security flaw where special characters in certificate names could be used to bypass security checks that limit which websites a certificate can be used for. This could allow attackers to use a certificate in ways it wasn't supposed to be used.

Technical detail

Node.js versions before 12.22.9, 14.18.3, 16.13.2, and 17.3.1 failed to properly escape Subject Alternative Names (SANs) when converting them to strings for hostname validation, enabling injection attacks that bypass name constraints in certificate chains. The vulnerability affects TLS/SSL peer certificate verification and was patched by escaping problematic characters in SANs.

Summary generated and translated by AI from the official description.
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.
Affected products
NodeJS · Node
Related CVEs — NodeJS Node

In the same product, most dangerous first.

CVE-2024-27983HIGHCVE-2024-27983EPSS 87.2%CVE-2022-32214—CVE-2022-32214EPSS 81.8%CVE-2021-22883—CVE-2021-22883EPSS 77.4%CVE-2022-32215—CVE-2022-32215EPSS 70.2%CVE-2019-15605—CVE-2019-15605EPSS 57.1%CVE-2020-8277—CVE-2020-8277EPSS 54.2%