Accepting arbitrary Subject Alternative Name (SAN) types, un… (CVE-2021-44531)

Summary

Vulnerability reported (CVE-2021-44531). Confidential information can be exposed externally.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-44531 has been found.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2021-44531" on the vendor's site.

CVE-2021-44531
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) has been reported.

📍 Affected scope

Check the vendor advisory for the affected versions.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami node-min

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"12.22.9"},{"introduced":"14.0.0"},{"fixed":"14.18.3"},{"introduced":"16.0.0"},{"fixed":"16.13.2"},{"introduced":"17.0.0"},{"fixed":"17.3.1"}]}]

Bitnami node

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"12.22.9"},{"introduced":"14.0.0"},{"fixed":"14.18.3"},{"introduced":"16.0.0"},{"fixed":"16.13.2"},{"introduced":"17.0.0"},{"fixed":"17.3.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2021-44531 nodejs Fixed in: 12.22.10-r0
Debian DEBIAN-CVE-2021-44531 nodejs Fixed in: 12.22.9~dfsg-1

References

advisory nodejs.org
advisory security.netapp.com
advisory debian.org
advisory oracle.com
advisory hackerone.com
advisory oracle.com
web nvd.nist.gov