First published: Thu Jun 02 2016(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/Chrome | <51.0.2704.79 | 51.0.2704.79 |
Ubuntu | =14.04 | |
Ubuntu | =15.10 | |
Ubuntu | =16.04 | |
Debian Linux | =8.0 | |
SUSE Linux | =42.1 | |
openSUSE | =13.2 | |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Workstation | =6.0 | |
SUSE Linux Enterprise Server | =12.0 | |
Google Chrome | <=51.0.2704.63 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1699 is classified as a high severity vulnerability affecting Google Chrome and other browsers using the Blink engine.
To fix CVE-2016-1699, update Google Chrome to version 51.0.2704.79 or later.
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.
CVE-2016-1699 can be exploited by remote attackers to bypass security mechanisms and execute arbitrary code.
There are no known workarounds for CVE-2016-1699 apart from updating the affected browser to a secure version.