LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44531: Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a par...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Vulnerable Node.js versions could trust a TLS certificate based on URI Subject Alternative Name data when hostname checking should not rely on that field. In the wrong PKI conditions, this could let an attacker impersonate a trusted service and undermine encrypted connection trust.

Executive priority

Treat this as a targeted trust-boundary risk, not a broad internet worm risk. Prioritize upgrades where Node.js handles outbound TLS to sensitive systems, internal services, identity providers, or regulated data paths.

Technical view

Node.js before 12.22.9, 14.18.3, 16.13.2, and 17.3.1 accepted URI SAN types during certificate hostname validation and matched allowed URI SANs incorrectly. The fix disables URI SAN handling for hostname checks, with a documented security-revert option.

Likely exposure

Exposure is most relevant for Node.js applications that initiate TLS connections or otherwise rely on Node certificate hostname verification, especially where private or enterprise PKI name constraints are used.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical abuse likely depends on certificate issuance, PKI constraints, and a vulnerable Node.js runtime performing hostname validation.

Researcher notes

The key issue is certificate name validation accepting URI SANs outside expected PKI semantics, enabling possible bypass of name-constrained intermediates. Evidence in the bundle is sufficient for affected-version triage but incomplete on exploit prevalence.

Mitigation direction

  • Upgrade Node.js to 12.22.9, 14.18.3, 16.13.2, 17.3.1, or later supported releases.
  • Check Node.js, Debian, Oracle, and product vendor advisories for environment-specific packages.
  • Avoid using the Node.js security-revert option unless a documented risk exception exists.
  • Inventory containers, serverless runtimes, build images, and packaged appliances that embed Node.js.

Validation and detection

  • Confirm runtime Node.js versions across production, CI, containers, and developer images.
  • Review TLS client code paths that depend on Node.js certificate hostname checks.
  • Check process flags for use of the documented security-revert option.
  • Verify vendor-supplied Node.js packages include the January 2022 security release fixes.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-295: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-44531 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NodeJSNode4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.