CVE-2016-1699: Medium severity ubuntu vulnerability
A parameter sanitization failure flaw was found in the DevTools component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=607939
External References:
http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html
Other sources
WebKit/Source/devtools/frontend/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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-1699?
CVE-2016-1699 is classified as a high severity vulnerability affecting Google Chrome and other browsers using the Blink engine.
How do I fix CVE-2016-1699?
To fix CVE-2016-1699, update Google Chrome to version 51.0.2704.79 or later.
Which software versions are affected by CVE-2016-1699?
CVE-2016-1699 affects Google Chrome versions prior to 51.0.2704.79 and certain Linux distributions like Ubuntu 14.04, 15.10, and 16.04.
What type of attack can exploit CVE-2016-1699?
CVE-2016-1699 can be exploited by remote attackers to bypass security mechanisms and execute arbitrary code.
Is there a workaround for CVE-2016-1699 while waiting for the update?
There are no known workarounds for CVE-2016-1699 apart from updating the affected browser to a secure version.