ua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an…
Summary
Vulnerability reported (CVE-2021-27292). Risk of unauthorized operations or information disclosure. Exploitable via User-Agent header. Mitigation: upgrade to 0.7.24 or later.
Original description
The description as published by the source.
ua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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-27292 has been found.
Attackers can target a specific entry point like User-Agent header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade the affected software to 0.7.24 or later.
If unsure, ask your IT team or search "CVE-2021-27292" on the vendor's site.
CVE-2021-27292
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: User-Agent header
Patched: 0.7.24 — apply immediately
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.
A vulnerability (unclassified) has been reported. Attackers reach the vulnerable code path via User-Agent header without authentication.
Check the vendor advisory for the affected versions. Attack surface: User-Agent header.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.7.24.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Apply patch patch
Upgrade to 0.7.24ステージング環境で 0.7.24 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch github.com
- patch github.com
- report gist.github.com