object-observe.js in Google V8, as used in Google Chrome before 45.0.2454.101, does not properly restrict method calls on access-checked objects, which allows remote attackers to bypass the Same Origin Policy via a (1) observe or (2) getNotifier call.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Chrome | * | 45.0.2454.93 (including) | |
Chromium-browser | Ubuntu | artful | * |
Chromium-browser | Ubuntu | bionic | * |
Chromium-browser | Ubuntu | cosmic | * |
Chromium-browser | Ubuntu | devel | * |
Chromium-browser | Ubuntu | precise | * |
Chromium-browser | Ubuntu | trusty | * |
Chromium-browser | Ubuntu | upstream | * |
Chromium-browser | Ubuntu | vivid | * |
Chromium-browser | Ubuntu | wily | * |
Chromium-browser | Ubuntu | xenial | * |
Chromium-browser | Ubuntu | yakkety | * |
Chromium-browser | Ubuntu | zesty | * |
Libv8 | Ubuntu | precise | * |
Libv8-3.14 | Ubuntu | artful | * |
Libv8-3.14 | Ubuntu | bionic | * |
Libv8-3.14 | Ubuntu | cosmic | * |
Libv8-3.14 | Ubuntu | devel | * |
Libv8-3.14 | Ubuntu | esm-apps/bionic | * |
Libv8-3.14 | Ubuntu | esm-apps/xenial | * |
Libv8-3.14 | Ubuntu | trusty | * |
Libv8-3.14 | Ubuntu | vivid | * |
Libv8-3.14 | Ubuntu | wily | * |
Libv8-3.14 | Ubuntu | xenial | * |
Libv8-3.14 | Ubuntu | yakkety | * |
Libv8-3.14 | Ubuntu | zesty | * |
Oxide-qt | Ubuntu | artful | * |
Oxide-qt | Ubuntu | trusty | * |
Oxide-qt | Ubuntu | upstream | * |
Oxide-qt | Ubuntu | vivid | * |
Oxide-qt | Ubuntu | vivid/stable-phone-overlay | * |
Oxide-qt | Ubuntu | wily | * |
Oxide-qt | Ubuntu | xenial | * |
Oxide-qt | Ubuntu | yakkety | * |
Oxide-qt | Ubuntu | zesty | * |
Red Hat Enterprise Linux 6 Supplementary | RedHat | chromium-browser-0:45.0.2454.101-1.el6 | * |
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: