Vulnerability in yargs-parser (CVE-2020-7608)
Summary
Vulnerability in yargs-parser (CVE-2020-7608). Risk of unauthorized operations or information disclosure. Exploitable via Object. Mitigation: upgrade to 5.0.1 or later.
Original description
The description as published by the source.
Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.
Recommendation
Upgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.
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-2020-7608 has been found in yargs-parser.
Attackers can target a specific entry point like Object over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade yargs-parser to 5.0.1 or later.
If unsure, ask your IT team or search "yargs-parser CVE-2020-7608" on the vendor's site.
CVE-2020-7608 (yargs-parser) — CWE-1321
Attack vector: local / no user interaction
Attack surface: Object / bar / baz
Patched: 5.0.1 — 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 (CWE-1321) exists in yargs-parser. Attackers reach the vulnerable code path via Object.
Check the vendor advisory for the affected versions of yargs-parser. Attack surface: Object / bar / baz.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.0.1.
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. Run grep -r 'yargs-parser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'yargs-parser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
yargs-parserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade yargs-parser to 5.0.1ステージング環境で 5.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-7608 node-yargs-parser Fixed in: 18.1.1-1
References
- advisory nvd.nist.gov
- package github.com
- web snyk.io
- web github.com
- web github.com
- web npmjs.com