dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-3105

HIGH · 9.3 CVSS v2.0 Published 2012-06-05
Fix available
A fix is available. Upgrade to after 2.9 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The glBufferData function in the WebGL implementation in Mozilla Firefox 4.x through 12.0, Firefox ESR 10.x before 10.0.5, Thunderbird 5.0 through 12.0, Thunderbird ESR 10.x before 10.0.5, and SeaMonkey before 2.10 does not properly mitigate an unspecified flaw in an NVIDIA driver, which allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors, a related issue to CVE-2011-3101.

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 confidence

A vulnerability in the WebGL glBufferData function in Firefox, Thunderbird, and SeaMonkey fails to properly mitigate an unspecified flaw in NVIDIA graphics drivers. This can lead to memory corruption allowing denial of service (application crash) or potentially remote code execution when rendering malicious WebGL content.

MitigationApply vendor-supplied patches by updating to Firefox 13.0+, Firefox ESR 10.0.5+, Thunderbird 13.0+, Thunderbird ESR 10.0.5+, or SeaMonkey 2.10+. As a workaround, disable WebGL in browser settings until updates can be applied.

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
FirefoxWeb browser
Affected:= 4.0= 4.0.1= 5.0= 5.0.1= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 8.0.1= 9.0
SeamonkeyApplication
Affected:<= 2.9= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1
ThunderbirdApplication
Affected:= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 9.0= 9.0.1= 10.0= 10.0.1= 10.0.2
Thunderbird EsrApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

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

  1. Identify the installed Mozilla product
    Open the application and navigate to Help > About (or check the application name in the system) to determine if it is Firefox, SeaMonkey, or Thunderbird.
    Affected if The product is Firefox, SeaMonkey, or Thunderbird.
  2. Check the installed version number
    In the application, go to Help > About to view the exact version number displayed.
    Affected if The version matches any of the affected versions: Firefox 4.0 through 9.0, SeaMonkey 1.0.x through 1.1 or 2.9 and below, Thunderbird 5.0 through 10.0.2, or Thunderbird ESR 10.0 through 10.0.4.
  3. Verify if WebGL is enabled
    In Firefox: type 'about:config' in the address bar, search for 'webgl.enabled_for_all_sites' or check through Options > Advanced > General > Enable WebGL. In SeaMonkey: check through Edit > Preferences > Advanced > Enable WebGL. In Thunderbird: check through Edit > Preferences > Advanced > General > Enable WebGL.
    Affected if WebGL is currently enabled in the browser settings.
  4. Check for NVIDIA graphics hardware
    Inspect the system hardware information or open the NVIDIA Control Panel to confirm an NVIDIA GPU is present.
    Affected if The system has an NVIDIA graphics card installed.

The environment is affected if any of the listed Firefox, SeaMonkey, or Thunderbird versions are installed, WebGL is enabled, and the system uses NVIDIA graphics hardware.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.9
Interim mitigation

Apply vendor-supplied patches by updating to Firefox 13.0+, Firefox ESR 10.0.5+, Thunderbird 13.0+, Thunderbird ESR 10.0.5+, or SeaMonkey 2.10+. As a workaround, disable WebGL in browser settings until updates can be applied.

Recommended fix High confidence

Upgrade to Firefox 12.0.1+/Firefox ESR 10.0.5+, Thunderbird 12.0.1+/Thunderbird ESR 10.0.5+, or SeaMonkey 2.10+ depending on product

  1. 1. Identify the exact Mozilla product and version currently installed (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, or SeaMonkey)
  2. 2. For Firefox 4.x-12.0 users: Upgrade to Firefox 12.0.1 or later
  3. 3. For Firefox ESR 10.x users: Upgrade to Firefox ESR 10.0.5 or later
  4. 4. For Thunderbird 5.0-12.0 users: Upgrade to Thunderbird 12.0.1 or later
  5. 5. For Thunderbird ESR 10.x users: Upgrade to Thunderbird ESR 10.0.5 or later
  6. 6. For SeaMonkey users on versions <= 2.9: Upgrade to SeaMonkey 2.10 or later
  7. 7. After upgrade, verify the WebGL implementation is functioning correctly
  8. 8. Confirm the version by checking Help > About in the application menu
Caveat Upgrading from older major versions may introduce UI changes and deprecated extensions; test critical workflows before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3105 — 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-3105 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