CVE-2017-5027

Description

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.

4.3

CVSS

Severity: Medium

CVSS 3.0 •

CVSS 2.0 •

EPSS 0.11%

Affected: n/a Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android

References

Link	Tags
https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html
https://crbug.com/661126

Frequently Asked Questions

What is the severity of CVE-2017-5027?: CVE-2017-5027 has been scored as a medium severity vulnerability.
How to fix CVE-2017-5027?: To fix CVE-2017-5027, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-5027 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2017-5027 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-5027?: CVE-2017-5027 affects n/a Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.