CVE-2012-4183
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 DOMSVGTests::GetRequiredFeatures 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 the DOMSVGTests::GetRequiredFeatures function in Mozilla products allows remote attackers to execute arbitrary code or cause heap memory corruption via unspecified vectors in SVG DOM processing.
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< 10.0.8< 16.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
- 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 Firefox installation and versionOn Linux, run 'firefox --version' or check the package manager (dpkg -l firefox | grep -i firefox or rpm -qa firefox). On Windows, check Help > About Firefox. On macOS, run 'firefox --version' or open Firefox and check Firefox > About Firefox.Affected if The installed version is earlier than 10.0.8 or between 10.0.8 and 15.x (any version less than 16.0)
-
Identify Thunderbird installation and versionOn Linux, run 'thunderbird --version' or check the package manager (dpkg -l thunderbird or rpm -qa thunderbird). On Windows, check Help > About Thunderbird. On macOS, run 'thunderbird --version' or open Thunderbird and check Thunderbird > About Thunderbird.Affected if Thunderbird is installed and the version is earlier than 10.0.8 (ESR) or earlier than 16.0 (non-ESR)
-
Confirm the vulnerability scopeThis vulnerability is in the DOMSVGTests::GetRequiredFeatures function used during SVG DOM processing. SVG processing is a built-in feature of Firefox and Thunderbird with no user-controllable on/off switch.Affected if The browser or email client processes SVG content (which occurs by default when viewing SVG images or SVG-based web content)
A system is affected if Firefox Thunderbird or SeaMonkey is installed with a version lower than 10.0.8 or any version from 10.0.8 through 15.x (less than 16.0), since the use-after-free flaw exists in the built-in SVG DOM processing component.
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 to Firefox 16.0+, Firefox ESR 10.0.8+, Thunderbird 16.0+, Thunderbird ESR 10.0.8+, or SeaMonkey 2.13+ to patch the vulnerability.
Firefox 16.0+ or Firefox ESR 10.0.8+; Thunderbird 16.0+ or Thunderbird ESR 10.0.8+; SeaMonkey 2.13+
- 1. Close all instances of the affected Mozilla product (Firefox, Thunderbird, or SeaMonkey)
- 2. For Firefox: Download Firefox 16.0 or later from the official Mozilla website (mozilla.org/firefox) or use your system's package manager
- 3. For Thunderbird: Download Thunderbird 16.0 or later from mozilla.org/thunderbird or use your system's package manager
- 4. For SeaMonkey: Download SeaMonkey 2.13 or later from mozilla.org/seamonkey or use your system's package manager
- 5. On Linux systems using package managers: Run 'sudo apt-get update && sudo apt-get upgrade' for Ubuntu/Debian, or 'sudo yum update' for RHEL/CentOS
- 6. Alternatively for RHEL systems: Run 'sudo yum update firefox thunderbird' to update only the Mozilla products
- 7. Restart the application after update completes
- 8. Verify the version by checking Help > About (Firefox/Thunderbird) or Help > About SeaMonkey to confirm the installed version is at or above the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4183 — 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-4183 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