CVE-2015-6760
chromium-browser: Improper error handling in libANGLE
Overview
Description
The Image11::map function in renderer/d3d/d3d11/Image11.cpp in libANGLE, as used in Google Chrome before 46.0.2490.71, mishandles mapping failures after device-lost events, which allows remote attackers to cause a denial of service (invalid read or write) or possibly have unspecified other impact via vectors involving a removed device.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Weakness: CWE-17
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
openSUSE 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ungoogled-chromium +1 | 113.0.5672.92-1.1 | openSUSE-SU-2024:12948-1 |
| Tumbleweed | chromedriver +1 | 55.0.2883.75-3.1 | openSUSE-SU-2024:10171-1 |
References
- googlechromereleases.blogspot.com http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2015-1912.html
- www.debian.org http://www.debian.org/security/2015/dsa-3376
- www.securityfocus.com http://www.securityfocus.com/bid/77071
- www.securitytracker.com http://www.securitytracker.com/id/1033816
- access.redhat.com https://access.redhat.com/security/cve/CVE-2015-6760
- chromium.googlesource.com https://chromium.googlesource.com/angle/angle.git/+/39939686b3731eaaf6c0b639ab64db0277c72475
- code.google.com https://code.google.com/p/chromium/issues/detail?id=519642
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2015-6760
- security.gentoo.org https://security.gentoo.org/glsa/201603-09
Show all 11 references
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.