ChromeWeb browser · Google
CVE-2012-2883
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSkia, as used in Google Chrome before 22.0.1229.79, 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, a different vulnerability than CVE-2012-2874.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOut-of-bounds write vulnerability in the Skia graphics library used in Google Chrome before version 22.0.1229.79. Remote attackers can trigger the vulnerability via crafted graphics data, leading to denial of service or potentially arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 22.0.1229.78= 22.0.1229.0= 22.0.1229.1= 22.0.1229.2= 22.0.1229.3= 22.0.1229.4= 22.0.1229.6= 22.0.1229.7= 22.0.1229.8= 22.0.1229.9= 22.0.1229.10= 22.0.1229.11= 12.1= 12.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionOpen chrome://version in the browser address bar or access Chrome menu > Help > About Google Chrome. Record the version number shown.Affected if Version is 22.0.1229.x where x is 0 through 11, or any version 22.0.1229.78 or lower
-
Verify Chrome is using Skia graphics libraryThe Skia library is built into Chrome's rendering pipeline. No separate check needed - if Chrome is running and rendering web content, Skia is in use.Affected if Chrome is actively used for web browsing (Skia is the default graphics renderer in affected Chrome versions)
-
Check installed Chrome package on OpenSUSEOn OpenSUSE systems, run 'rpm -qa | grep chrome' or 'zypper se google-chrome' to list installed Chrome packages, then 'rpm -q --info google-chrome' to see version details.Affected if Google Chrome package version matches the affected version range (< 22.0.1229.79)
You are affected if Google Chrome version is 22.0.1229.78 or lower, or any 22.0.1229.0 through 22.0.1229.11 version, and you use Chrome for web browsing which triggers the Skia graphics library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Google Chrome to version 22.0.1229.79 or later. If using Skia in a custom application, update to a patched Skia library version that addresses this out-of-bounds write.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2883 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-2883 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data