CVE-2015-2731
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 CSPService::ShouldLoad function in the microtask implementation in Mozilla Firefox before 39.0, Firefox ESR 38.x before 38.1, and Thunderbird before 38.1 allows remote attackers to execute arbitrary code by leveraging client-side JavaScript that triggers removal of a DOM object on the basis of a Content Policy.
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 confidenceA use-after-free vulnerability in Mozilla Firefox and Thunderbird's Content Security Policy (CSP) implementation allows remote attackers to execute arbitrary code. The flaw occurs in the CSPService::ShouldLoad function during DOM object removal triggered by JavaScript, causing freed memory to be accessed.
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<= 38.1.0= 31.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3= 38.0= 31.1= 31.2= 31.3= 31.4= 31.5= 31.6.0= 31.7.0<= 38.0.1= 11.3CVSS 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 Firefox versionOn Windows, check Help > About Firefox. On Linux, run 'firefox --version' or check the package manager. On macOS, run 'firefox --version' or check Application info.Affected if The installed version is 38.1.0 or earlier, or exactly matches 31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1, 31.5.2, 31.5.3, or 38.0
-
Identify installed Firefox ESR versionOn Windows, check Help > About Firefox. On Linux, run 'firefox --version' or check the package manager.Affected if The installed version is exactly 31.1, 31.2, 31.3, 31.4, 31.5, 31.6.0, or 31.7.0
-
Identify installed Thunderbird versionOn Windows, check Help > About Thunderbird. On Linux, run 'thunderbird --version' or check the package manager. On macOS, run 'thunderbird --version' or check Application info.Affected if The installed version is 38.0.1 or earlier
-
Determine if Content Security Policy is in useInspect web applications or pages being accessed for CSP headers (Content-Security-Policy HTTP response headers) or meta tags. Check browser developer tools or proxy logs for CSP enforcement.Affected if CSP headers or meta tags are present and being enforced - the vulnerable code path in CSPService::ShouldLoad is only triggered when CSP is active
You are affected if you are running Firefox 38.1.0 or earlier (or specific point versions listed), Firefox ESR 31.x through 31.7.0, Thunderbird 38.0.1 or earlier, or Oracle Solaris 11.3 with bundled Firefox, and you process Content Security Policy headers.
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 · scopedUpgrade affected products to Firefox 39.0, Firefox ESR 38.1, Thunderbird 38.1, or later versions. This is a client-side vulnerability requiring software updates rather than network configuration changes.
Firefox 39.0+ or Firefox ESR 38.1+ or Thunderbird 38.1+
- 1. Close all instances of Firefox, Thunderbird, or related Mozilla products
- 2. Back up bookmarks, passwords, and important profile data
- 3. Download Firefox 39.0 or later from mozilla.org
- 4. Run the installer and follow prompts to upgrade
- 5. Alternatively, use the application's built-in update mechanism (Help > About > Check for Updates)
- 6. For Firefox ESR 31.x systems, upgrade to Firefox ESR 38.1 or later
- 7. For Thunderbird users, upgrade to Thunderbird 38.1 or later
- 8. Restart the application and verify the version in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2731 — 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-2731 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