CVE-2016-1699 — Improper Access Control in Google Chrome

CWE-284 — Improper Access Control7 documents7 sources
Severity
6.5MEDIUMNVD
EPSS
0.9%
top 24.31%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
9
Google ChromeCanonical Ubuntu LinuxDebian Linux+6 more
Timeline
PublishedJun 5
Latest updateMay 14

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.

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitability: 2.8 | Impact: 3.6

Affected Packages6 packages

▶NVDgoogle/chrome51.0.2704.63
▶NVDopensuse/leap42.1

Also affects: Debian Linux 8.0, Linux Enterprise 12.0, Ubuntu Linux 14.04, 15.10, 16.04

🔴Vulnerability Details

3
GHSA
GHSA-m9mc-h49h-mj7c: WebKit/Source/devtools/front_end/devtools↗2022-05-14
▶
OSV
CVE-2016-1699: WebKit/Source/devtools/front_end/devtools↗2016-06-06
▶
CVEList
CVE-2016-1699: WebKit/Source/devtools/front_end/devtools↗2016-06-05
▶

📋Vendor Advisories

2
Ubuntu
Oxide vulnerabilities↗2016-06-06
▶
Red Hat
chromium-browser: parameter sanitization failure in devtools↗2016-06-01
▶

💬Community

1
Bugzilla
CVE-2016-1699 chromium-browser: parameter sanitization failure in devtools↗2016-06-02
▶
CVE-2016-1699 — Improper Access Control in Google | cvebase