dbcve.org
ChromeOperating system · Google

CVE-2012-5129

HIGH · 7.5 CVSS v2.0 Published 2012-12-04
Fix available
A fix is available. Upgrade to after 21.0.1180.57 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Heap-based buffer overflow in the WebGL subsystem in Google Chrome OS before 23.0.1271.94 allows remote attackers to cause a denial of service (GPU process crash) or possibly have unspecified other impact via unknown vectors.

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 · moderate confidence

Heap-based buffer overflow vulnerability in the WebGL graphics rendering subsystem of Google Chrome OS versions prior to 23.0.1271.94. The flaw allows remote attackers to trigger the overflow via malicious WebGL content, causing GPU process crashes (denial of service) or potentially achieving arbitrary code execution.

MitigationUpgrade Chrome OS to version 23.0.1271.94 or later to patch the heap overflow in the WebGL subsystem. Consider disabling WebGL in interim if immediate patching is not feasible.

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
ChromeOperating system
Affected:= 23.0.1271.91= 23.0.1271.92
Chrome OsOperating system
Affected:<= 21.0.1180.57

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Navigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version number
    Affected if The displayed version is 23.0.1271.91 or 23.0.1271.92 exactly, or falls within the affected range for Chrome OS (versions prior to 23.0.1271.94 on Chrome OS <= 21.0.1180.57)
  2. Verify WebGL status in Chrome
    Navigate to chrome://settings and search for 'WebGL', or inspect the WebGL rendering context via chrome://gpu/ to confirm whether WebGL is currently enabled
    Affected if WebGL is enabled and the browser version matches the affected versions listed in the CVE
  3. Check Chrome OS version if applicable
    On Chrome OS devices, access chrome://settings or the system settings menu to view the Chrome OS version information
    Affected if The Chrome OS version is 21.0.1180.57 or earlier, and WebGL is accessible/enabled

A user is affected if their Google Chrome version is 23.0.1271.91 or 23.0.1271.92, or if their Chrome OS version is 21.0.1180.57 or earlier, and WebGL is enabled in the browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 21.0.1180.57
Interim mitigation

Upgrade Chrome OS to version 23.0.1271.94 or later to patch the heap overflow in the WebGL subsystem. Consider disabling WebGL in interim if immediate patching is not feasible.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5129 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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