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.
References
Link | Resource |
---|---|
http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html | Release Notes Vendor Advisory |
http://lists.opensuse.org/opensuse-updates/2015-04/msg00040.html | Third Party Advisory |
http://www.debian.org/security/2015/dsa-3238 | Third Party Advisory |
http://www.securityfocus.com/bid/74227 | Third Party Advisory VDB Entry |
https://code.google.com/p/chromium/issues/detail?id=455953 | Exploit Vendor Advisory |
Configurations
History
No history.
Information
Published : 2015-04-19 10:59
Updated : 2024-02-04 18:35
NVD link : CVE-2015-3336
Mitre link : CVE-2015-3336
CVE.ORG link : CVE-2015-3336
JSON object : View
Products Affected
opensuse
- opensuse
debian
- debian_linux
- chrome
CWE
CWE-264
Permissions, Privileges, and Access Controls