ChromeWeb browser · Google
CVE-2012-5143
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 · uneditedInteger overflow in Google Chrome before 23.0.1271.97 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to PPAPI image buffers.
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 confidenceInteger overflow vulnerability in Google Chrome's PPAPI (Pepper Plugin API) image buffer handling before version 23.0.1271.97. The overflow occurs when processing image buffers in the PPAPI implementation, allowing remote attackers to cause denial of service or potentially execute arbitrary code via crafted vectors.
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
<= 23.0.1271.96= 23.0.1271.0= 23.0.1271.1= 23.0.1271.2= 23.0.1271.3= 23.0.1271.4= 23.0.1271.5= 23.0.1271.6= 23.0.1271.7= 23.0.1271.8= 23.0.1271.9= 23.0.1271.10= 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command lineAffected if The version shown is 23.0.1271.96 or lower, or any version from 23.0.1271.0 through 23.0.1271.10
-
Verify PPAPI plugin support is enabledNavigate to chrome://plugins and locate the PPAPI (Pepper) section; ensure plugins like Adobe Flash Player (PPAPI) are enabledAffected if PPAPI-based plugins are enabled and in use
-
Confirm the image buffer feature is in useThe vulnerability affects PPAPI image buffer handling - this is triggered when processing image data through the Pepper Plugin API, commonly used by PDF viewers or Flash pluginsAffected if Any application or plugin that uses PPAPI to handle image buffers is actively running
You are affected if your Chrome version is 23.0.1271.96 or any version from 23.0.1271.0 through 23.0.1271.10 AND you have PPAPI-based plugins enabled that process image data.
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.
dbcve · scopedUpdate Google Chrome to version 23.0.1271.97 or later to obtain the patch that adds proper bounds checking on PPAPI image buffer allocations.
Chrome 23.0.1271.97 or later; openSUSE security updates for 12.1/12.2
- For Chrome (Windows/Mac): Open Chrome, go to Help > About Google Chrome, and let it check for and install updates. Restart after updating to version 23.0.1271.97 or later.
- For Chrome (Linux): Use your package manager to update the chrome-browser package (e.g., sudo apt-get update && sudo apt-get upgrade for Debian/Ubuntu, or equivalent for your distribution).
- For openSUSE 12.1/12.2: Run 'sudo zypper update' or 'sudo zypper patch' to apply the security update from openSUSE repositories.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5143 — 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-5143 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