CVE-2012-3960
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 mozSpellChecker::SetCurrentDictionary 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 or cause a denial of service (heap memory corruption) 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 mozSpellChecker::SetCurrentDictionary in Firefox, Thunderbird, and SeaMonkey allows remote attackers to execute arbitrary code or cause heap memory corruption. The vulnerability occurs when memory is freed but still accessed, potentially allowing controlled memory reallocation and 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< 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.
-
Check installed Firefox versionRun 'firefox --version' or check the package manager (dpkg -l firefox, rpm -qi firefox)Affected if Version is < 10.0.7 OR >= 10.0 and < 15.0 (includes 10.x through 14.x)
-
Check installed SeaMonkey versionRun 'seamonkey --version' or check the package manager (dpkg -l seamonkey, rpm -qi seamonkey)Affected if Version is < 2.12
-
Check installed Thunderbird versionRun 'thunderbird --version' or check the package manager (dpkg -l thunderbird, rpm -qi thunderbird)Affected if Version is < 10.0.7 OR >= 10.0 and < 15.0 (includes 10.x through 14.x)
-
Verify spell checker is enabled in the applicationIn Firefox/Thunderbird/SeaMonkey, go to Preferences > Advanced > General > Check spelling, or inspect about:config for 'spellchecker.enable' settingAffected if Spell checking is enabled (value is true) - the vulnerability requires the spell checker component to be loaded and active
-
Check OS version for Red Hat systemsRun 'cat /etc/redhat-release' to identify the Red Hat Enterprise Linux versionAffected if Version is exactly 5.0, 6.0, or 6.3 (these specific point releases are affected)
You are affected if you run Firefox < 10.0.7 or >= 10.0 with version < 15.0, SeaMonkey < 2.12, or the specific Red Hat/Ubuntu point releases listed, AND the spell checker component is enabled in the application.
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
Upgrade to Firefox 15.0+, Firefox ESR 10.0.7+, Thunderbird 15.0+, Thunderbird ESR 10.0.7+, SeaMonkey 2.12+, or later patched versions to remediate this vulnerability.
Firefox 15.0, Firefox ESR 10.0.7, SeaMonkey 2.12, or Thunderbird 15.0/ESR 10.0.7 depending on product in use
- Identify the affected application (Firefox, Firefox ESR, SeaMonkey, or Thunderbird) installed on the system
- For Red Hat Enterprise Linux systems: Run 'yum update firefox' or 'yum update seamonkey' to apply the security update
- For Ubuntu Linux systems: Run 'apt-get update && apt-get upgrade firefox' or 'apt-get upgrade seamonkey'
- For openSUSE systems: Run 'zypper update' to apply security patches
- After updating, verify the installed version matches the fixed release (Firefox 15.0, Firefox ESR 10.0.7, SeaMonkey 2.12, or Thunderbird 15.0/ESR 10.0.7)
- Restart the browser/application after updating to ensure the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3960 — 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-3960 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