CVE-2015-1213
NoneCVSS
—
EPSS
1.5%
Published
Mar 9, 2015
CISA due date
—
Cloudanix analysis
An image-handling problem in older versions of Chrome could let a malicious website crash the browser or run unauthorized code on a visitor's computer.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Remote Code Execution
- Component
- Library
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Out-of-bounds write in SkBitmap::ReadRawPixels during Skia bitmap filter processing allows memory corruption that can lead to denial of service or arbitrary code execution.
Why it matters to the business
Browser instability or successful exploitation can interrupt user workflows, expose sensitive data, and require emergency patching across large fleets of endpoints.
How an attack unfolds
An attacker hosts a specially crafted web page or image resource that reaches the vulnerable Skia code path in Chrome; when the browser parses the content, the out-of-bounds write occurs, enabling memory manipulation for code execution or crash.
How to fix it
Upgrade Google Chrome to version 41.0.2272.76 or newer; apply the latest stable channel updates as soon as they become available.
How to confirm the fix worked
Verify installed Chrome version is at or above 41.0.2272.76; attempt reproduction with known trigger vectors in a controlled test environment and confirm absence of crash or corruption.
Typical attack path
- Deliver malicious HTML or image content via a web page or embedded resource
- Trigger Skia bitmap decoding and filtering routines
- Cause out-of-bounds write to corrupt memory
- Leverage corruption for code execution or denial of service
How to detect it
Search browser crash logs and process dumps for Skia-related faults; monitor for unexpected terminations when rendering web content containing bitmap data.
What your security team should do
- Prioritize browser updates across all managed endpoints
- Enable automatic updates where possible
- Review web proxy or endpoint logs for unusual Chrome crash patterns
The record
The SkBitmap::ReadRawPixels function in core/SkBitmap.cpp in the filters implementation in Skia, as used in Google Chrome before 41.0.2272.76, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger an out-of-bounds write operation.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Mageia:4 | chromium-browser-stable | 0 | 41.0.2272.101-1.mga4 |
| Red Hat:rhel_extras:6 | chromium-browser | 0 | 0:41.0.2272.76-1.el6_6 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | 0 | 0:41.0.2272.76-1.el6_6 |
| Ubuntu:14.04:LTS | chromium-browser | 0 | 41.0.2272.76-0ubuntu0.14.04.1.1076 |
| Ubuntu:14.04:LTS | oxide-qt | 0 | 1.5.5-0ubuntu0.14.04.3 |
| openSUSE:Tumbleweed | chromium | 0 | 55.0.2883.75-3.1 |
| openSUSE:Tumbleweed | chromium | 0 | 113.0.5672.92-1.1 |
Related vulnerabilities
- CVE-2015-1291 The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in Blink, as… Also affects chromium-browser-stable
- CVE-2015-1266 content/browser/webui/content_web_ui_controller_factory.cc in Google Chrome before… Also affects chromium-browser-stable
- CVE-2015-1253 core/html/parser/HTMLConstructionSite.cpp in the DOM implementation in Blink, as used in… Also affects chromium-browser-stable
- CVE-2015-1243 Use-after-free vulnerability in the MutationObserver::disconnect function in… Also affects chromium-browser-stable
- CVE-2015-1235 The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in the HTML… Also affects chromium-browser-stable
- CVE-2015-1233 Google Chrome before 41.0.2272.118 does not properly handle the interaction of IPC, the… Also affects chromium-browser-stable
- CVE-2015-1209 Use-after-free vulnerability in the VisibleSelection::nonBoundaryShadowTreeRootNode… Also affects chromium-browser-stable
- CVE-2014-7904 Buffer overflow in Skia, as used in Google Chrome before 39.0.2171.65, allows remote… Also affects chromium-browser-stable