CVE-2012-3959
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 nsRangeUpdater::SelAdjDeleteNode 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 Mozilla Firefox, Thunderbird, SeaMonkey, and their ESR versions allows remote attackers to execute arbitrary code or cause heap memory corruption via memory corruption in the nsRangeUpdater::SelAdjDeleteNode function when handling unspecified DOM manipulation vectors.
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= 6.0= 7.0CVSS 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 Mozilla productsCheck for Firefox, Thunderbird, or SeaMonkey on the system. On Linux, run: dpkg -l | grep -E 'firefox|thunderbird|seamonkey' or rpm -qa | grep -E 'firefox|thunderbird|seamonkey'. On Windows, check Program Files for Mozilla folders. On macOS, check /Applications for these applications.Affected if None of these products are installed (not affected); if any are present, continue to version check.
-
Determine Firefox versionRun 'firefox --version' from command line, or open Firefox and navigate to Help > About Firefox. Record the version number displayed (e.g., 10.0.6, 14.0.1).Affected if Version is below 15.0, OR version is 10.0.x where x is less than 7 (10.0.0 through 10.0.6). Example: 10.0.6 is affected, 10.0.7 is not, 15.0 is not.
-
Determine Thunderbird versionRun 'thunderbird --version' from command line, or open Thunderbird and navigate to Help > About Thunderbird. Record the version number displayed.Affected if Version is below 15.0, OR version is 10.0.x where x is less than 7 (10.0.0 through 10.0.6). Example: 10.0.6 is affected, 10.0.7 is not, 15.0 is not.
-
Determine SeaMonkey versionRun 'seamonkey --version' from command line, or open SeaMonkey and navigate to Help > About SeaMonkey. Record the version number displayed.Affected if Version is below 2.12 (any 2.x version where x < 12, or any 1.x version). Example: 2.11 is affected, 2.12 is not.
The user is affected if they have Firefox < 15.0 (or 10.0.x below 10.0.7), Thunderbird < 15.0 (or 10.0.x below 10.0.7), or SeaMonkey < 2.12 installed.
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 · scoped10.0.715.0
Upgrade to Firefox 15.0+, Firefox ESR 10.0.7+, Thunderbird 15.0+, Thunderbird ESR 10.0.7+, or SeaMonkey 2.12+ to patch the use-after-free in nsRangeUpdater::SelAdjDeleteNode.
Firefox 15.0+ (or Firefox ESR 10.0.7+)
- Back up all critical data and bookmarks before proceeding
- Close all instances of Firefox, Thunderbird, or SeaMonkey running on the system
- For Debian/Ubuntu systems: Run 'apt-get update && apt-get upgrade' to install available security updates
- For RHEL/CentOS systems: Run 'yum update' or 'yum update firefox' to apply available security patches
- For openSUSE systems: Run 'zypper update' to apply available security patches
- Alternatively, download Firefox 15.0 or later from the official Mozilla website (mozilla.org)
- Install the updated package or run the downloaded installer
- Restart the application and verify the version by navigating to Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3959 — 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-3959 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