CVE-2012-3963
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 js::gc::MapAllocToTraceKind function in Mozilla Firefox before 15.0, Firefox ESR 10.x before 10.0.7, Thunderbird before 15.0, Thunderbird ESR 10.x before 10.0.7, and SeaMonkey before 2.12 allows remote attackers to execute arbitrary code via unspecified 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 · high confidenceUse-after-free vulnerability in the js::gc::MapAllocToTraceKind function of Mozilla's JavaScript garbage collection subsystem allows remote attackers to execute arbitrary code by freeing memory that is still being accessed.
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< 15.0>= 10.0, < 10.0.7= 5.0= 6.0= 6.3= 5.0= 6.0= 6.3= 5.0= 6.0= 10.04= 11.04= 11.10= 12.04< 2.12CVSS 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 installed Firefox versionOpen Firefox, go to Help > About Firefox, or run: firefox --versionAffected if Version is below 10.0, OR between 10.0 and 10.0.7 (excluding 10.0.7), OR between 10.0.7 and 15.0 (excluding 15.0)
-
Identify installed SeaMonkey versionOpen SeaMonkey, go to Help > About SeaMonkey, or run: seamonkey --versionAffected if Version is below 2.12 (any 2.x version below 2.12)
-
Check if JavaScript is enabled in the browserIn Firefox/SeaMonkey, go to Options/Preferences > Content and verify 'Enable JavaScript' is checked. This is the default setting.Affected if JavaScript is enabled (default state). The vulnerability exists in the JS garbage collector and triggers when JavaScript executes.
-
Check OS-level browser packages on RHEL/CentOSRun: rpm -qa | grep -E 'firefox|seamonkey' to list installed Mozilla browser packages and their versionsAffected if Any Firefox or SeaMonkey package version matches the affected version ranges for the OS (5.0, 6.0, 6.3 for RHEL variants)
-
Check OS-level browser packages on Ubuntu/DebianRun: dpkg -l | grep -E 'firefox|seamonkey' or check Software Center for installed Mozilla browser packagesAffected if Any Firefox or SeaMonkey package version matches the affected version ranges for Ubuntu (10.04, 11.04, 11.10, 12.04)
Your environment is affected if you are running Firefox below 15.0 (excluding 10.0.7 and ESR 10.0.7+), or SeaMonkey below 2.12, with JavaScript enabled (the default).
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 · scoped2.1210.0.715.0
Update affected Mozilla products to patched versions: Firefox 15.0+, Firefox ESR 10.0.7+, Thunderbird 15.0+, Thunderbird ESR 10.0.7+, or SeaMonkey 2.12+. Apply via vendor auto-update or manual installation.
Firefox 15.0, Firefox ESR 10.0.7, Thunderbird 15.0, Thunderbird ESR 10.0.7, or SeaMonkey 2.12
- Identify which Mozilla product is installed: Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, or SeaMonkey
- Check the current installed version using the system's package manager (e.g., rpm -q firefox, dpkg -l firefox, or yum info firefox)
- For Fedora/Red Hat Enterprise Linux systems: Run 'yum update firefox' or 'yum update thunderbird' or 'yum update seamonkey' to install the patched version
- For Ubuntu/Debian systems: Run 'apt-get update && apt-get install firefox' (or thunderbird/seamonkey) to get the latest available fixed version
- Restart the browser or email client after the update completes
- Verify the installed version matches or exceeds the fixed release: Firefox 15.0+, Firefox ESR 10.0.7+, Thunderbird 15.0+, Thunderbird ESR 10.0.7+, or SeaMonkey 2.12+
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-3963 — 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-3963 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