dbcve.org
FirefoxWeb browser · Mozilla

CVE-2015-2722

HIGH · 10.0 CVSS v2.0 Published 2015-07-06
Fix available
A fix is available. Upgrade to after 38.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Use-after-free vulnerability in the CanonicalizeXPCOMParticipant function in Mozilla Firefox before 39.0 and Firefox ESR 31.x before 31.8 and 38.x before 38.1 allows remote attackers to execute arbitrary code via vectors involving attachment of an XMLHttpRequest object to a shared worker.

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 confidence

Use-after-free vulnerability in the CanonicalizeXPCOMParticipant function in Mozilla Firefox allows remote attackers to execute arbitrary code via vectors involving attachment of an XMLHttpRequest object to a shared worker.

MitigationUpgrade to Firefox 39.0 or later, or Firefox ESR 31.8/38.1 or later to remediate this vulnerability.

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
Affected:= 31.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3= 38.0<= 38.1.0
Firefox EsrWeb browser
Affected:= 31.1= 31.2= 31.3= 31.4= 31.5= 31.6.0= 31.7.0
SolarisOperating system
Affected:= 11.3
Suse Linux Enterprise Software Development KitApplication
Affected:= 12.0
Suse Linux Enterprise DesktopOperating system
Affected:= 12.0
Suse Linux Enterprise ServerOperating system
Affected:= 11= 12.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Firefox version
    Open Firefox, click the menu button, select Help > About Firefox. Alternatively, navigate to about:support in the address bar to see the version number under Application Basics.
    Affected if The version is 31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1, 31.5.2, 31.5.3, 38.0, or any version from 38.0.1 through 38.1.0 inclusive.
  2. Check installed Firefox ESR version
    Open Firefox ESR, click the menu button, select Help > About Firefox ESR. Alternatively, navigate to about:support in the address bar to see the version number.
    Affected if The version is 31.1, 31.2, 31.3, 31.4, 31.5, 31.6.0, or 31.7.0.
  3. Verify JavaScript is enabled
    Navigate to about:config in the Firefox address bar. Search for javascript.enabled and confirm the value is set to true.
    Affected if JavaScript must be enabled for the vulnerable code path involving XMLHttpRequest and shared workers to be exploitable.
  4. Confirm shared worker usage in the environment
    Review web application code or browser console output for usage of SharedWorker API. Check if any web applications load scripts that create shared workers using 'new SharedWorker()'.
    Affected if The vulnerability is triggered specifically when an XMLHttpRequest object is attached to a shared worker, so usage of shared workers is required for exploitation.

A user is affected if they are running Firefox versions 31.0 through 31.5.3, 38.0 through 38.1.0, or Firefox ESR versions 31.1 through 31.7.0, with JavaScript enabled and where web pages can use shared workers with XMLHttpRequest objects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 38.1.0
Interim mitigation

Upgrade to Firefox 39.0 or later, or Firefox ESR 31.8/38.1 or later to remediate this vulnerability.

Recommended fix High confidence

Firefox ESR 31.8 (for 31.x users), Firefox ESR 38.1 (for 38.x users), or Firefox 39.0+ (for non-ESR users)

  1. 1. Check the currently installed Firefox version by navigating to Help > About Firefox (or using 'firefox --version' in terminal)
  2. 2. For Firefox ESR 31.x users: Upgrade to Firefox ESR 31.8 or later (or migrate to a supported ESR branch)
  3. 3. For Firefox ESR 38.x users: Upgrade to Firefox ESR 38.1 or later
  4. 4. For Firefox (non-ESR) users: Upgrade to Firefox 39.0 or later
  5. 5. After upgrade, restart Firefox to apply the changes
  6. 6. Verify the new version is installed: Help > About Firefox should show the fixed version
Caveat Upgrading to a newer Firefox version may change browser behavior, remove legacy add-on compatibility, or alter UI. Test critical workflows before deploying broadly in production environments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2722 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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