Vulnerability in angular (CVE-2019-10768)
Summary
Vulnerability in angular (CVE-2019-10768). Data can be tampered with by attackers. Mitigation: upgrade to 1.7.9 or later.
Original description
The description as published by the source.
Versions of angular prior to 1.7.9 are vulnerable to prototype pollution. The deprecated API function merge() does not restrict the modification of an Object's prototype in the , which may allow an attacker to add or modify an existing property that will exist on all objects.
Recommendation
Upgrade to version 1.7.9 or later. The function was already deprecated and upgrades are not expected to break functionality.
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-2019-10768 has been found in angular.
Data can be tampered with by attackers.
What to do: upgrade angular to 1.7.9 or later.
If unsure, ask your IT team or search "angular CVE-2019-10768" on the vendor's site.
CVE-2019-10768 (angular) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.7.9 — 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 angular.
Check the vendor advisory for the affected versions of angular.
Severity: ?. Data can be tampered with by attackers.
Update to 1.7.9.
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 'angular' . 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 'angular' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
angularを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade angular to 1.7.9ステージング環境で 1.7.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-2019-10768 angular.js Fixed in: 1.7.9-1
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web lists.apache.org
- web lists.apache.org
- web snyk.io