CVE-2016-1699

UnknownEPSS 1.38%

Last modified

CVE-2016-1699 is a vulnerability of currently unknown severity. WebKit/Source/devtools/front_end/devtools.js in the Developer Tools (aka DevTools) subsystem in Blink, as used in Google Chrome before 51.0.2704.79, does not ensure that the remoteFrontendUrl parameter is associated with a chrome-devtools-frontend.appspot.com URL, which allows remote attackers to bypass intended access restrictions via a crafted URL.. EPSS estimates a 1.38% chance of exploitation in the next 30 days.

Description

WebKit/Source/devtools/front_end/devtools.js in the Developer Tools (aka DevTools) subsystem in Blink, as used in Google Chrome before 51.0.2704.79, does not ensure that the remoteFrontendUrl parameter is associated with a chrome-devtools-frontend.appspot.com URL, which allows remote attackers to bypass intended access restrictions via a crafted URL.

Metrics

EPSS Probability
1.38%

68.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux15.10
CanonicalUbuntu Linux16.04
DebianDebian Linux8.0
OpensuseLeap42.1
OpensuseOpensuse13.2
RedhatEnterprise Linux Desktop6.0
RedhatEnterprise Linux Server6.0
RedhatEnterprise Linux Workstation6.0
SuseLinux Enterprise12.0
GoogleChrome<= 51.0.2704.63

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-1699?
WebKit/Source/devtools/front_end/devtools.js in the Developer Tools (aka DevTools) subsystem in Blink, as used in Google Chrome before 51.0.2704.79, does not ensure that the remoteFrontendUrl parameter is associated with a chrome-devtools-frontend.appspot.com URL, which allows remote attackers to bypass intended access restrictions via a crafted URL.
How severe is CVE-2016-1699?
Severity scoring for CVE-2016-1699 is pending analysis. The EPSS model estimates a 1.38% probability of exploitation in the next 30 days.
How do I fix CVE-2016-1699?
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.

Are you affected by CVE-2016-1699?

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

Scan your code now

Source: NVD / NIST