Is CVE-2020-7676 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-7676 being exploited in the wild.

How severe is CVE-2020-7676?

Low severity, with a CVSS score of 3.1, published 18 June 2020.

Which products and versions are affected?

Google Angular.js prior to 1.8.0; angular (npm) SEMVER:introduced=0,fixed=1.8.0.

Is there a fix for CVE-2020-7676?

Yes. angular (npm): upgrade to 1.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-7676 attacked?

It is attacked over the network.

Am I affected by CVE-2020-7676?

Check whether you run Google Angular.js or 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.

CVE-2020-7676: Angular Cross-site Scripting in HTML sanitization

CVE-2020-7676 · Severity: low · CVSS 3.1 · Published 2020-06-18

Angular's HTML sanitization feature, used to prevent malicious scripts in user-supplied content, contains a flaw that allows attackers to bypass the sanitization through regex manipulation. An attacker can craft malicious HTML containing option/select elements that, when processed, converts previously sanitized code into executable JavaScript, leading to session hijacking, credential theft, or malware distribution.

Technologies: angular (npm). Vendors: Google, npm.

Quick answers

Is CVE-2020-7676 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-7676 being exploited in the wild.
How severe is CVE-2020-7676?: Low severity, with a CVSS score of 3.1, published 18 June 2020.
Which products and versions are affected?: Google Angular.js prior to 1.8.0; angular (npm) SEMVER:introduced=0,fixed=1.8.0.
Is there a fix for CVE-2020-7676?: Yes. angular (npm): upgrade to 1.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-7676 attacked?: It is attacked over the network.
Am I affected by CVE-2020-7676?: Check whether you run Google Angular.js or 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.8.0 or later
```
npm install angular@1.8.0
```

Technical details

The vulnerability is a Cross-site Scripting (XSS) flaw in Angular.js's regex-based HTML replacement mechanism used for input sanitization. The root cause is that wrapping <option> elements in <select> elements changes HTML parsing behavior, allowing previously sanitized code to become unsanitized. The vulnerability affects Angular versions prior to 1.8.0 and requires user interaction (application must process attacker-controlled HTML). An attacker with network access can inject malicious payloads into an application using the vulnerable Angular version; the application's inability to properly sanitize the crafted input allows script execution in the victim's browser. The fix was merged in version 1.8.0 (commit 2df43c07779137d1bddf7f3b282a1287a8634acd) and made available on May 27, 2020.

Affected products

Google Angular.js prior to 1.8.0

Identifiers

CVE-2020-7676
GHSA-mhp6-pxh8-r675

Timeline

2020-06-08: disclosed: Published on NVD
2020-05-27: patched: Fix merged as PR #17028 into Angular.js master branch; released in version 1.8.0
2020-06-18: advisory: GHSA-mhp6-pxh8-r675 published

References

https://github.com/angular/angular.js/pull/17028

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.