dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-0443

HIGH · 10.0 CVSS v2.0 Published 2012-02-01
Fix available
A fix is available. Upgrade to after 2.7 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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox 4.x through 9.0, Thunderbird 5.0 through 9.0, and SeaMonkey before 2.7 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code 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

Multiple memory corruption vulnerabilities in the Mozilla browser engine (Gecko) affecting Firefox 4.x-9.0, Thunderbird 5.0-9.0, and SeaMonkey before 2.7. Attackers can trigger memory corruption leading to denial of service or potentially achieve arbitrary code execution through unknown vectors in the rendering engine.

MitigationApply vendor-supplied patches by upgrading to Firefox 10+, Thunderbird 10+, or SeaMonkey 2.7+. Alternatively, disable or restrict JavaScript execution in untrusted contexts as a defense-in-depth measure.

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= 8.0= 8.0.1= 9.0
ThunderbirdApplication
Affected:= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 8.0= 9.0
SeamonkeyApplication
Affected:<= 2.7= 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
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 checks

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

  1. Identify installed Mozilla product
    Check for Firefox, Thunderbird, or SeaMonkey installation by looking for the respective executable in standard locations (e.g., C:\Program Files\Mozilla Firefox\firefox.exe, C:\Program Files\Mozilla Thunderbird\thunderbird.exe, C:\Program Files\SeaMonkey\seamonkey.exe) or by using system utilities like 'where firefox' / 'where thunderbird' / 'where seamonkey' on Windows, or 'which firefox' / 'which thunderbird' / 'which seamonkey' on Unix-like systems
    Affected if No Mozilla product is installed (not affected)
  2. Determine Firefox version
    Run 'firefox --version' from command line, or open Firefox and navigate to Help > About Firefox, or inspect the firefox.exe file properties. Compare the version number against the affected list: 4.0, 4.0.1, 5.0, 5.0.1, 6.0, 6.0.1, 6.0.2, 7.0, 8.0, 8.0.1, or 9.0
    Affected if Installed version matches any of 4.0 through 9.0 (inclusive)
  3. Determine Thunderbird version
    Run 'thunderbird --version' from command line, or open Thunderbird and navigate to Help > About Thunderbird, or inspect the thunderbird.exe file properties. Compare the version number against the affected list: 5.0, 6.0, 6.0.1, 6.0.2, 7.0, 8.0, or 9.0
    Affected if Installed version matches any of 5.0 through 9.0 (inclusive)
  4. Determine SeaMonkey version
    Run 'seamonkey --version' from command line, or open SeaMonkey and navigate to Help > About SeaMonkey, or inspect the seamonkey.exe file properties. Compare the version number against the affected list: 1.0 through 1.1.x (all versions) or 2.0 through 2.7
    Affected if Installed version is 2.7 or lower, or any 1.x version (1.0 through 1.1)

The environment is affected if Firefox 4.0-9.0, Thunderbird 5.0-9.0, or SeaMonkey 2.7 or earlier (including all 1.x versions) is installed and the rendering engine is in use.

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

Apply vendor-supplied patches by upgrading to Firefox 10+, Thunderbird 10+, or SeaMonkey 2.7+. Alternatively, disable or restrict JavaScript execution in untrusted contexts as a defense-in-depth measure.

Recommended fix High confidence

Firefox 10.0, Thunderbird 10.0, or SeaMonkey 2.7 (or later stable releases within those product lines)

  1. 1. Check current installed version of Firefox, Thunderbird, or SeaMonkey by navigating to Help > About (or Application > About in SeaMonkey)
  2. 2. Close all instances of the affected application
  3. 3. Download the latest stable version from the official Mozilla repository at https://www.mozilla.org/
  4. 4. For Firefox: Download Firefox 10.0 or later from https://www.mozilla.org/en-US/firefox/all/
  5. 5. For Thunderbird: Download Thunderbird 10.0 or later from https://www.mozilla.org/en-US/thunderbird/all/
  6. 6. For SeaMonkey: Download SeaMonkey 2.7 or later from https://www.mozilla.org/en-US/projects/seamonkey/
  7. 7. Run the installer and follow the prompts to complete the upgrade
  8. 8. Restart the application after installation completes
Caveat This is a major version jump from Firefox 5.x to 10.0 and Thunderbird 6.x to 10.0; some legacy add-ons/extensions may be incompatible with the newer version and will need updates or replacement

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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