FirefoxWeb browser · Mozilla
CVE-2014-1592
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 nsHtml5TreeOperation function in xul.dll in Mozilla Firefox before 34.0, Firefox ESR 31.x before 31.3, Thunderbird before 31.3, and SeaMonkey before 2.31 allows remote attackers to execute arbitrary code by adding a second root element to an HTML5 document during parsing.
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 nsHtml5TreeOperation function in xul.dll allows remote code execution by adding a second root element to an HTML5 document during parsing, causing the parser to reference freed memory.
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
FirefoxWeb browser
<= 31.2<= 33.0<= 2.30<= 31.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 productCheck for presence of Firefox, Thunderbird, or SeaMonkey in installed programs or by locating their executable files (e.g., firefox.exe, thunderbird.exe, seamonkey.exe)Affected if Any of Firefox, Thunderbird, or SeaMonkey is installed
-
Determine Firefox versionRun 'firefox --version' from command line, or right-click firefox.exe > Properties > Details > File Version, or check Help > About FirefoxAffected if Version is 31.2 or lower, or between 31.3 and 33.0 (non-ESR versions before 34.0)
-
Determine Thunderbird versionRun 'thunderbird --version' from command line, or right-click thunderbird.exe > Properties > Details > File Version, or check Help > About ThunderbirdAffected if Version is 31.2 or lower
-
Determine SeaMonkey versionRun 'seamonkey --version' from command line, or right-click seamonkey.exe > Properties > Details > File Version, or check Help > About SeaMonkeyAffected if Version is 2.30 or lower
-
Confirm xul.dll presenceLocate xul.dll in the application installation directory (typically in the same folder as the main executable)Affected if The vulnerable xul.dll file exists in the product directory
A user is affected if they have Firefox versions 31.2 or lower, Firefox 33.0 or lower (non-ESR), Thunderbird 31.2 or lower, or SeaMonkey 2.30 or lower installed, as these contain the vulnerable xul.dll with the nsHtml5TreeOperation use-after-free flaw.
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.
From vendor dataUpgrade affected products to Firefox 34.0+, Firefox ESR 31.3+, Thunderbird 31.3+, or SeaMonkey 2.31+ to apply the patch.
Fix this in Firefox
Scoped from the published advisory
- 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-2014-1592 — 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-2014-1592 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