FirefoxWeb browser · Mozilla
CVE-2015-0804
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 · uneditedThe HTMLSourceElement::BindToTree function in Mozilla Firefox before 37.0 does not properly constrain a data type after omitting namespace validation during certain tree-binding operations, which allows remote attackers to execute arbitrary code or cause a denial of service (use-after-free) via a crafted HTML document containing a SOURCE element.
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's HTMLSourceElement::BindToTree function. The function fails to properly constrain a data type after omitting namespace validation during tree-binding operations for SOURCE elements, leading to memory corruption that can be exploited for arbitrary 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
FirefoxWeb browser
<= 36.0.4
Ubuntu LinuxOperating system
= 12.04= 14.04= 14.10= 13.1= 13.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Check installed Firefox version on Windows or MacOpen Firefox and navigate to Help > About Firefox, or run 'firefox --version' from command lineAffected if Version displayed is 36.0.4 or earlier (any version <= 36.0.4)
-
Check Firefox package version on UbuntuRun command: dpkg -l | grep firefox or apt-cache policy firefoxAffected if Installed firefox package version is <= 36.0+build1-0ubuntu0.12.04.1 for 12.04, <= 36.0+build1-0ubuntu0.14.10.1 for 14.04/14.10, or any version before the security update for your Ubuntu release
-
Check Firefox package version on OpenSUSERun command: rpm -qi MozillaFirefox or zypper info MozillaFirefoxAffected if Installed MozillaFirefox package version is <= 36.0.4-49.1 for openSUSE 13.1/13.2 or earlier than the patched version for your release
-
Identify if SOURCE elements are in use (optional context)Inspect web pages loaded in Firefox for HTML5 video or audio elements that use <source> tags - the vulnerability triggers during tree-binding of these elementsAffected if The vulnerable code path in HTMLSourceElement::BindToTree is exercised when SOURCE elements are bound to the document tree; however version check alone is sufficient to determine exposure
A system is affected if Mozilla Firefox version 36.0.4 or earlier (or an equivalent vulnerable package version on Ubuntu/OpenSUSE) is installed, regardless of whether specific SOURCE elements are present in browsing sessions.
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 Mozilla Firefox to version 37.0 or later to patch the vulnerability. Organizations should deploy the update through their patch management systems and verify compatibility with enterprise applications.
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-2015-0804 — 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-2015-0804 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