CVE-2012-4179
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 nsHTMLCSSUtils::CreateCSSPropertyTxn function in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbird before 16.0, Thunderbird ESR 10.x before 10.0.8, and SeaMonkey before 2.13 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's nsHTMLCSSUtils::CreateCSSPropertyTxn function allows remote attackers to execute arbitrary code or cause heap memory corruption via unspecified vectors involving CSS property transaction handling.
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< 10.0.8< 16.0= 10.04= 11.04= 11.10= 12.04= 5.0= 6.0= 6.3= 5.0= 6.0= 5.0= 6.0= 6.0< 10.0.8CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 productRun 'dpkg -l | grep -E "firefox|thunderbird|seamonkey"' on Debian/Ubuntu, or 'rpm -qa | grep -E "firefox|thunderbird|seamonkey"' on RHEL/CentOS, or check Program Files on WindowsAffected if No Mozilla product found means not applicable; if found, proceed to version check
-
Check Firefox versionRun 'firefox --version' or 'firefox -v' from command line, or look at Help > About in the Firefox UIAffected if Version is less than 10.0.8 OR between 10.0.8 and 15.x (i.e., < 16.0) indicates vulnerability
-
Check Thunderbird versionRun 'thunderbird --version' or 'thunderbird -v' from command line, or look at Help > About in the Thunderbird UIAffected if Version is less than 10.0.8 indicates vulnerability (ESR versions < 10.0.8)
-
Check SeaMonkey versionRun 'seamonkey --version' or look at Help > About in SeaMonkey UIAffected if Version is less than 2.13 indicates vulnerability
You are affected if you have Firefox < 10.0.8 or Firefox 10.0.8-15.x, Thunderbird ESR < 10.0.8, or SeaMonkey < 2.13 installed and actively using 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 · scoped10.0.816.0
Upgrade affected products to Firefox 16.0+, Thunderbird 16.0+, SeaMonkey 2.13+, or Firefox/Thunderbird ESR 10.0.8+ to obtain vendor patches.
Firefox 16.0+ (or Firefox ESR 10.0.8+); Thunderbird 16.0+ (or Thunderbird ESR 10.0.8+); SeaMonkey 2.13+
- Identify the installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) and its current version using the application's 'About' menu or command line (e.g., firefox --version, thunderbird --version)
- If running Firefox ESR 10.x, upgrade to Firefox ESR 10.0.8 or later
- If running Firefox (non-ESR) below 16.0, upgrade to Firefox 16.0 or later
- If running Thunderbird ESR 10.x, upgrade to Thunderbird ESR 10.0.8 or later
- If running Thunderbird (non-ESR) below 16.0, upgrade to Thunderbird 16.0 or later
- If running SeaMonkey below 2.13, upgrade to SeaMonkey 2.13 or later
- Use the operating system's package manager to update (e.g., apt-get update && apt-get upgrade for Debian/Ubuntu, yum update for RHEL/CentOS) or download directly from mozilla.org
- Restart the application after upgrade to ensure the new version is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4179 — 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 sources- www.mozilla.org
- bugzilla.mozilla.org
- lists.opensuse.org
- rhn.redhat.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- www.debian.org
- www.debian.org
- www.debian.org
- www.mandriva.com
- www.ubuntu.com
- exchange.xforce.ibmcloud.com
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-4179 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