Strix
26.1K

CVE-2016-5135

UnknownEPSS 1.62%

Last modified

CVE-2016-5135 is a vulnerability of currently unknown severity. WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp in Blink, as used in Google Chrome before 52.0.2743.82, does not consider referrer-policy information inside an HTML document during a preload request, which allows remote attackers to bypass the Content Security Policy (CSP) protection mechanism via a crafted web site, as demonstrated by a "Content-Security-Policy: referrer origin-when-cross-origin" header that overrides a "<META name='referrer' content='no-referrer'>" element.. EPSS estimates a 1.62% chance of exploitation in the next 30 days.

Description

WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp in Blink, as used in Google Chrome before 52.0.2743.82, does not consider referrer-policy information inside an HTML document during a preload request, which allows remote attackers to bypass the Content Security Policy (CSP) protection mechanism via a crafted web site, as demonstrated by a "Content-Security-Policy: referrer origin-when-cross-origin" header that overrides a "<META name='referrer' content='no-referrer'>" element.

Metrics

EPSS Probability
1.62%

72.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
GoogleChrome<= 51.0.2704.106

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-5135?
WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp in Blink, as used in Google Chrome before 52.0.2743.82, does not consider referrer-policy information inside an HTML document during a preload request, which allows remote attackers to bypass the Content Security Policy (CSP) protection mechanism via a crafted web site, as demonstrated by a "Content-Security-Policy: referrer origin-when-cross-origin" header that overrides a "<META name='referrer' content='no-referrer'>" element.
How severe is CVE-2016-5135?
Severity scoring for CVE-2016-5135 is pending analysis. The EPSS model estimates a 1.62% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5135?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2016

View all 2016CVEs →

Are you affected by CVE-2016-5135?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST