Quick answers
- Is CVE-2019-10768 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-10768 being exploited in the wild.
- How severe is CVE-2019-10768?
- Low severity, with a CVSS score of 3.1, published 20 November 2019.
- Which products and versions are affected?
- angular (npm) SEMVER:introduced=0,fixed=1.7.9.
- Is there a fix for CVE-2019-10768?
- Yes. angular (npm): upgrade to 1.7.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-10768 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-10768?
- Check whether you run angular (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- angular (npm): upgrade to 1.7.9 or later
npm install angular@1.7.9
Technical details
The vulnerability is a prototype pollution flaw in the angular.merge() function (CWE-1321, CWE-20, CWE-915). The deprecated merge() API does not properly restrict modification of an Object's __proto__ property during deep merging operations, allowing an attacker to pollute the Object prototype with arbitrary properties. This is a network-reachable vulnerability requiring no authentication or user interaction; an attacker can craft malicious input containing __proto__ keys to inject properties that persist across all objects. The fix (version 1.7.9) explicitly blocks __proto__ from being merged, and this was already deprecated code so upgrades should not break existing functionality.
Affected products
- Google Angular before 1.7.9
Identifiers
- CVE-2019-10768
- GHSA-89mq-4x47-5v83
Timeline
- 2019-11-20: disclosed: Advisory published
- 2019-11-07: patched: Fix merged in PR #16913