dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-0468

HIGH · 10.0 CVSS v2.0 Published 2012-04-25
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 browser engine in Mozilla Firefox 4.x through 11.0, Thunderbird 5.0 through 11.0, and SeaMonkey before 2.9 allows remote attackers to cause a denial of service (assertion failure and memory corruption) or possibly execute arbitrary code via vectors related to jsval.h and the js::array_shift function.

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

Memory corruption vulnerability in the SpiderMonkey JavaScript engine's js::array_shift function related to jsval.h handling. Allows remote attackers to cause denial of service through assertion failures and memory corruption, or potentially achieve arbitrary code execution via crafted JavaScript.

MitigationUpgrade affected Mozilla products (Firefox 11.0 and later, Thunderbird 11.0 and later, SeaMonkey 2.9 and later) to patched versions that address this JavaScript engine flaw.

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

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 the installed Mozilla product
    Check whether Firefox, Thunderbird, or SeaMonkey is installed on the system. On Windows, look in Program Files. On Linux, check package manager or /usr/lib. On macOS, check /Applications.
    Affected if Any of these three products is installed
  2. Determine the Firefox version
    For Firefox: Open menu > Help > About Firefox, or run 'firefox --version' from command line. Note the exact version number.
    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 the Thunderbird version
    For Thunderbird: Open menu > Help > About Thunderbird, or run 'thunderbird --version' from command line. Note the exact version number.
    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 the SeaMonkey version
    For SeaMonkey: Open menu > Help > About SeaMonkey, or run 'seamonkey --version' from command line. Note the exact version number.
    Affected if The version is 2.9 or earlier, or any 1.0.x version (1.0 through 1.1)

You are affected if any of these Mozilla products is installed and its version matches one of the specific versions listed in the affected ranges, since the vulnerability exists in the SpiderMonkey JavaScript engine for those exact versions.

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

Upgrade affected Mozilla products (Firefox 11.0 and later, Thunderbird 11.0 and later, SeaMonkey 2.9 and later) to patched versions that address this JavaScript engine flaw.

Recommended fix High confidence

Firefox 12.0+, Thunderbird 12.0+, or SeaMonkey 2.9+

  1. 1. Identify the affected Mozilla product (Firefox, Thunderbird, or SeaMonkey) currently installed
  2. 2. Backup any critical local data as a precautionary measure
  3. 3. For Firefox users: Download and install Firefox 12.0 or later from the official Mozilla website (mozilla.org)
  4. 4. For Thunderbird users: Download and install Thunderbird 12.0 or later from the official Mozilla website (mozilla.org)
  5. 5. For SeaMonkey users: Download and install SeaMonkey 2.9 or later from the official Mozilla website (mozilla.org)
  6. 6. After installation, verify the version by checking About in the application menu
  7. 7. Ensure JavaScript is enabled in the browser settings to allow proper functionality
Caveat Upgrading may change UI elements, remove support for older extensions/plugins, or alter default settings; ensure compatibility with existing workflows

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
  • 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-0468 — 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-0468 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