Strix
26.1K

CVE-2016-5137

UnknownEPSS 1.26%

Last modified

CVE-2016-5137 is a vulnerability of currently unknown severity. The CSPSource::schemeMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 52.0.2743.82, does not apply http :80 policies to https :443 URLs and does not apply ws :80 policies to wss :443 URLs, which makes it easier for remote attackers to determine whether a specific HSTS web site has been visited by reading a CSP report. NOTE: this vulnerability is associated with a specification change after CVE-2016-1617 resolution.. EPSS estimates a 1.26% chance of exploitation in the next 30 days.

Description

The CSPSource::schemeMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 52.0.2743.82, does not apply http :80 policies to https :443 URLs and does not apply ws :80 policies to wss :443 URLs, which makes it easier for remote attackers to determine whether a specific HSTS web site has been visited by reading a CSP report. NOTE: this vulnerability is associated with a specification change after CVE-2016-1617 resolution.

Metrics

EPSS Probability
1.26%

65.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-5137?
The CSPSource::schemeMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 52.0.2743.82, does not apply http :80 policies to https :443 URLs and does not apply ws :80 policies to wss :443 URLs, which makes it easier for remote attackers to determine whether a specific HSTS web site has been visited by reading a CSP report. NOTE: this vulnerability is associated with a specification change after CVE-2016-1617 resolution.
How severe is CVE-2016-5137?
Severity scoring for CVE-2016-5137 is pending analysis. The EPSS model estimates a 1.26% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5137?
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-5137?

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

Scan your code now

Source: NVD / NIST