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