ChromeWeb browser · Google
CVE-2012-2819
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 · uneditedThe texSubImage2D implementation in the WebGL subsystem in Google Chrome before 20.0.1132.43 does not properly handle uploads to floating-point textures, which allows remote attackers to cause a denial of service (assertion failure and application crash) or possibly have unspecified other impact via a crafted web page, as demonstrated by certain WebGL performance tests, aka rdar problem 11520387.
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 confidenceThis vulnerability exists in Google Chrome's WebGL implementation, specifically in the texSubImage2D function. When uploading data to floating-point textures, the function fails to properly handle the operation, causing an assertion failure that leads to application crash. Attackers can exploit this by tricking users into visiting crafted web pages that trigger the faulty code path.
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
<= 20.0.1132.42= 20.0.1132.0= 20.0.1132.1= 20.0.1132.2= 20.0.1132.3= 20.0.1132.4= 20.0.1132.5= 20.0.1132.6= 20.0.1132.7= 20.0.1132.8= 20.0.1132.9= 20.0.1132.10CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 if Google Chrome is installedOpen Chrome and navigate to chrome://version, or on command line run 'google-chrome --version' or 'chrome --version'Affected if Google Chrome is not installed - the vulnerability does not apply
-
Determine installed Chrome versionNavigate to chrome://version in the browser address bar and note the version number displayed under 'Google Chrome'Affected if Version falls outside 20.0.1132.0 through 20.0.1132.42 (including any version <= 20.0.1132.42) - not affected
-
Verify WebGL is enabledNavigate to chrome://flags in the browser, search for 'WebGL', and check if the feature is enabled or disabledAffected if WebGL is disabled - the vulnerable code path is not reachable, reducing risk
-
Confirm floating-point texture usage contextThis is a specific WebGL implementation flaw triggered when using texSubImage2D with floating-point textures (EXT_color_buffer_float or OES_texture_float). Check any WebGL applications or pages loaded for texture format usage.Affected if WebGL is used with floating-point textures on affected versions - vulnerable to crash via the assertion failure
User is affected if Google Chrome version 20.0.1132.0 through 20.0.1132.42 is installed, WebGL is enabled, and floating-point texture operations via texSubImage2D are performed.
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 20.0.1132.43 or later to obtain the patched WebGL implementation.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2819 — 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-2819 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