dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-2760

HIGH · 9.3 CVSS v2.0 Published 2010-09-09
Fix available
A fix is available. Upgrade to after 3.5.11 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 nsTreeSelection function in Mozilla Firefox before 3.5.12 and 3.6.x before 3.6.9, Thunderbird before 3.0.7 and 3.1.x before 3.1.3, and SeaMonkey before 2.0.7 might allow remote attackers to execute arbitrary code via vectors involving a XUL tree selection, related to a "dangling pointer vulnerability." NOTE: this issue exists because of an incomplete fix for CVE-2010-2753.

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 nsTreeSelection function in Mozilla products allows remote attackers to execute arbitrary code via XUL tree selection vectors. The flaw stems from a dangling pointer caused by incomplete fix for CVE-2010-2753.

MitigationDeploy vendor patches: Firefox 3.5.12+/3.6.9+, Thunderbird 3.0.7+/3.1.3+, SeaMonkey 2.0.7+ or later versions.

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:= 3.6= 3.6.2= 3.6.3= 3.6.4= 3.6.6= 3.6.7= 3.6.8<= 3.5.11= 1.0= 1.0.1= 1.0.2= 1.0.3
SeamonkeyApplication
Affected:<= 2.0.6= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1
ThunderbirdApplication
Affected:<= 3.0.6= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8

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

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

  1. Identify installed Mozilla product
    Check the application name in the system: look for Firefox, Thunderbird, or SeaMonkey in installed programs or running processes
    Affected if Any of these three products is installed
  2. Determine product version
    For Firefox: go to Help > About Firefox. For Thunderbird: go to Help > About Thunderbird. For SeaMonkey: go to Help > About SeaMonkey. Alternatively, check the application executable properties or version file
    Affected if Version cannot be determined or does not match a patched release
  3. Compare version against affected Firefox range
    If Firefox is installed, compare the version to: 3.6 (all minor versions .0-.8), 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, 3.6.8, or any 3.5.x up to 3.5.11, or 1.0.x-1.0.3
    Affected if Installed version matches any of these exact versions or falls within the <=3.5.11 or 3.6.x ranges listed
  4. Compare version against affected SeaMonkey range
    If SeaMonkey is installed, compare to: any version <=2.0.6, or versions 1.0 through 1.1 (all 1.0.x point releases)
    Affected if Installed version is <=2.0.6 or is a 1.0.x/1.1 version
  5. Compare version against affected Thunderbird range
    If Thunderbird is installed, compare to: any version <=3.0.6, or versions 0.1 through 0.8 (all 0.x point releases)
    Affected if Installed version is <=3.0.6 or falls in the 0.x range through 0.8

The environment is affected if any of Firefox (3.5.x through 3.6.8, or 1.0.x-1.0.3), SeaMonkey (1.0.x-1.1 or <=2.0.6), or Thunderbird (0.x through 0.8, or <=3.0.6) is installed at one of the specific versions listed in the affected ranges.

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 3.5.11
Interim mitigation

Deploy vendor patches: Firefox 3.5.12+/3.6.9+, Thunderbird 3.0.7+/3.1.3+, SeaMonkey 2.0.7+ or later versions.

Recommended fix High confidence

Firefox 3.6.9 (or 3.5.12), SeaMonkey 2.0.7, Thunderbird 3.0.7 or 3.1.3; or latest stable versions

  1. For Firefox 3.6.x users: Upgrade to Firefox 3.6.9 or later
  2. For Firefox 3.5.x users: Upgrade to Firefox 3.5.12 or later
  3. For SeaMonkey users on version 1.x or 2.x: Upgrade to SeaMonkey 2.0.7 or later
  4. For Thunderbird 3.0.x users: Upgrade to Thunderbird 3.0.7 or later
  5. For Thunderbird 3.1.x users: Upgrade to Thunderbird 3.1.3 or later
  6. Alternatively, consider upgrading to the latest stable versions of each product which include this security fix
Caveat These are security patch releases with minimal expected breaking changes; however, some legacy extensions or plugins may not be compatible with newer minor versions

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2760 — 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-2010-2760 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