Vulnerability in json8 (CVE-2020-7770)
Summary
Vulnerability in json8 (CVE-2020-7770). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.3 or later.
Original description
The description as published by the source.
This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution.
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-7770 has been found in json8.
Successful exploitation can lead to full system takeover.
What to do: upgrade json8 to 1.0.3 or later.
If unsure, ask your IT team or search "json8 CVE-2020-7770" on the vendor's site.
CVE-2020-7770 (json8) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.3 — 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 json8.
Check the vendor advisory for the affected versions of json8.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.0.3.
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 'json8' . 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 'json8' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
json8を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade json8 to 1.0.3ステージング環境で 1.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web snyk.io
- web npmjs.com