Google Chrome before 42.0.2311.90 does not always ask the user before proceeding with CONTENT_SETTINGS_TYPE_FULLSCREEN and CONTENT_SETTINGS_TYPE_MOUSELOCK changes, which allows user-assisted remote attackers to cause a denial of service (UI disruption) by constructing a crafted HTML document containing JavaScript code with requestFullScreen and requestPointerLock calls, and arranging for the user to access this document with a file: URL.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Chrome | * | 42.0.2311.60 (including) | |
| Chromium-browser | Ubuntu | devel | * |
| Chromium-browser | Ubuntu | lucid | * |
| Chromium-browser | Ubuntu | precise | * |
| Chromium-browser | Ubuntu | trusty | * |
| Chromium-browser | Ubuntu | upstream | * |
| Chromium-browser | Ubuntu | utopic | * |
| Chromium-browser | Ubuntu | vivid | * |
| Chromium-browser | Ubuntu | wily | * |
References
- http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00040.html
- http://www.debian.org/security/2015/dsa-3238
- http://www.securityfocus.com/bid/74227
- https://code.google.com/p/chromium/issues/detail?id=455953
- http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00040.html
- http://www.debian.org/security/2015/dsa-3238
- http://www.securityfocus.com/bid/74227
- https://code.google.com/p/chromium/issues/detail?id=455953