Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 8 | chromium-browser | 42.0.2311.90-1~deb8u1 | DSA-3238-1 |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 14.04 LTS | chromium-browser | 43.0.2357.81-0ubuntu0.14.04.1.1089 | — |
Advisories 1
- DSA-3238-1 chromium-browser - security update Debian Security (DSA / DLA) · Mar 9, 2026
References
- DSA-3238 vendor-advisory
- 74227 vdb-entry
- openSUSE-SU-2015:0748 vendor-advisory
- http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html
- https://code.google.com/p/chromium/issues/detail?id=455953