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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Ubuntu_linux | Canonical | 14.04 (including) | 14.04 (including) |
| Ubuntu_linux | Canonical | 15.10 (including) | 15.10 (including) |
| Ubuntu_linux | Canonical | 16.04 (including) | 16.04 (including) |
| Debian_linux | Debian | 8.0 (including) | 8.0 (including) |
| Leap | Opensuse | 42.1 (including) | 42.1 (including) |
| Opensuse | Opensuse | 13.2 (including) | 13.2 (including) |
| Enterprise_linux_desktop | Redhat | 6.0 (including) | 6.0 (including) |
| Enterprise_linux_server | Redhat | 6.0 (including) | 6.0 (including) |
| Enterprise_linux_workstation | Redhat | 6.0 (including) | 6.0 (including) |
| Linux_enterprise | Suse | 12.0 (including) | 12.0 (including) |
| Red Hat Enterprise Linux 6 Supplementary | RedHat | chromium-browser-0:51.0.2704.79-1.el6 | * |
| Chromium-browser | Ubuntu | devel | * |
| Chromium-browser | Ubuntu | precise | * |
| Chromium-browser | Ubuntu | trusty | * |
| Chromium-browser | Ubuntu | upstream | * |
| Chromium-browser | Ubuntu | wily | * |
| Chromium-browser | Ubuntu | xenial | * |
| Oxide-qt | Ubuntu | devel | * |
| Oxide-qt | Ubuntu | trusty | * |
| Oxide-qt | Ubuntu | upstream | * |
| Oxide-qt | Ubuntu | vivid/stable-phone-overlay | * |
| Oxide-qt | Ubuntu | wily | * |
| Oxide-qt | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: