dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-1952

HIGH · 9.3 CVSS v2.0 Published 2012-07-18
Fix available
A fix is available. Upgrade to after 2.10 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 nsTableFrame::InsertFrames function in Mozilla Firefox 4.x through 13.0, Firefox ESR 10.x before 10.0.6, Thunderbird 5.0 through 13.0, Thunderbird ESR 10.x before 10.0.6, and SeaMonkey before 2.11 does not properly perform a cast of a frame variable during processing of mixed row-group and column-group frames, which might allow remote attackers to execute arbitrary code via a crafted web site.

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

Use-after-free or type confusion vulnerability in nsTableFrame::InsertFrames function where an improper cast of a frame variable occurs during processing of mixed row-group and column-group frames in table rendering, leading to memory corruption that can be exploited for arbitrary code execution.

MitigationUpdate to patched versions: Firefox 13.0.1+, Firefox ESR 10.0.6+, Thunderbird 13.0.1+, Thunderbird ESR 10.0.6+, or SeaMonkey 2.11+. For legacy systems, disable JavaScript and restrict web content exposure.

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
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= 10.0.5
SeamonkeyApplication
Affected:<= 2.10= 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

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 installed Mozilla product
    Check the application name in Add/Remove Programs (Windows), the .app bundle (Mac), or package manager (Linux). Look for Firefox, Thunderbird, or SeaMonkey.
    Affected if The installed product is Firefox, Thunderbird, or SeaMonkey from the affected product list.
  2. Determine Firefox version
    In Firefox, navigate to Help > About Firefox (or go to about:support). The version number displays on the page that opens.
    Affected if The version is 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, or 9.0.
  3. Determine Thunderbird version
    In Thunderbird, navigate to Help > About Thunderbird. The version number displays on the page that opens.
    Affected if The version is 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, or 10.0.2.
  4. Determine Thunderbird ESR version
    In Thunderbird ESR, navigate to Help > About Thunderbird. The version number displays on the page that opens.
    Affected if The version is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, or 10.0.5.
  5. Determine SeaMonkey version
    In SeaMonkey, navigate to Help > About SeaMonkey. The version number displays on the page that opens.
    Affected if The version is 2.10 or below, or any 1.0.x through 1.1.x version.

If the installed product is Firefox 4.0-9.0, Thunderbird 5.0-10.0.2, Thunderbird ESR 10.0-10.0.5, or SeaMonkey <=2.10 or 1.x, the environment is vulnerable to this use-after-free flaw in table frame processing.

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.10
Interim mitigation

Update to patched versions: Firefox 13.0.1+, Firefox ESR 10.0.6+, Thunderbird 13.0.1+, Thunderbird ESR 10.0.6+, or SeaMonkey 2.11+. For legacy systems, disable JavaScript and restrict web content exposure.

Recommended fix High confidence

Firefox 14.0+ (or Firefox ESR 10.0.6+), Thunderbird 14.0+ (or Thunderbird ESR 10.0.6+), SeaMonkey 2.11+

  1. 1. Backup your profile data (bookmarks, passwords, preferences) located in your profile directory
  2. 2. Close all instances of Firefox, Thunderbird, or SeaMonkey
  3. 3. Download the latest stable version from the official Mozilla website (mozilla.org) or use your system's package manager
  4. 4. For Linux systems: run 'sudo zypper update mozilla Firefox' or 'sudo apt-get upgrade firefox' depending on your distribution
  5. 5. For Windows/Mac: run the installer and follow prompts to upgrade
  6. 6. After upgrade, verify the version by checking Help > About Firefox/Thunderbird/SeaMonkey
Caveat Ensure compatibility with existing extensions/plugins before upgrading; some legacy add-ons may not work on newer versions

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

Fix this in Firefox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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