CVE-2012-0469
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 · uneditedUse-after-free vulnerability in the mozilla::dom::indexedDB::IDBKeyRange::cycleCollection::Trace function in Mozilla Firefox 4.x through 11.0, Firefox ESR 10.x before 10.0.4, Thunderbird 5.0 through 11.0, Thunderbird ESR 10.x before 10.0.4, and SeaMonkey before 2.9 allows remote attackers to execute arbitrary code via vectors related to crafted IndexedDB data.
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 confidenceUse-after-free vulnerability in Mozilla's IndexedDB IDBKeyRange cycle collection trace function allows remote attackers to execute arbitrary code via crafted IndexedDB data. The flaw occurs when freed memory is accessed after being deallocated during the collection cycle, leading to potential code execution.
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= 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= 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= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4<= 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.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Mozilla productCheck if Firefox, Thunderbird, or SeaMonkey is installed. On Windows, look in Program Files. On macOS, check /Applications. On Linux, run which firefox thunderbird seamonkey or check your package manager.Affected if Any of these products are installed
-
Determine Firefox versionRun 'firefox --version' from command line, or open Firefox and go to Help > About Firefox. On macOS, run '/Applications/Firefox.app/Contents/MacOS/firefox --version'.Affected if 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
-
Determine Thunderbird versionRun 'thunderbird --version' from command line, or open Thunderbird and go to Help > About Thunderbird. On macOS, run '/Applications/Thunderbird.app/Contents/MacOS/thunderbird --version'.Affected if 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
-
Determine Thunderbird ESR versionRun 'thunderbird --version' and note if it is an ESR release. ESR versions typically show '10.0' series with extended support.Affected if Version is 10.0, 10.0.1, 10.0.2, 10.0.3, or 10.0.4 (ESR editions)
-
Determine SeaMonkey versionRun 'seamonkey --version' from command line, or open SeaMonkey and go to Help > About SeaMonkey.Affected if Version is 2.9 or lower, or exactly 1.0 through 1.1 series (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)
The environment is affected if the installed Firefox, Thunderbird, Thunderbird ESR, or SeaMonkey version matches any of the specific versions listed in the affected products and versions for CVE-2012-0469.
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.
dbcve · scopedUpdate affected Mozilla products (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, SeaMonkey) to the patched versions that address this vulnerability.
Firefox 12.0+, Thunderbird 12.0+, Thunderbird ESR 10.0.4+, SeaMonkey 2.9+
- 1. Back up all critical user data and browser profiles before performing the upgrade
- 2. For Firefox: Download and install Firefox 12.0 or later from the official Mozilla website (mozilla.org)
- 3. For Thunderbird: Download and install Thunderbird 12.0 or later from the official Mozilla website
- 4. For Thunderbird ESR: Ensure version 10.0.4 or later is installed, or upgrade to the latest ESR release
- 5. For SeaMonkey: Upgrade to SeaMonkey 2.9 or later from the SeaMonkey project website
- 6. After upgrade, verify the installed version matches the fixed release by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0469 — 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-0469 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