dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-2762

MEDIUM · 6.8 CVSS v2.0 Published 2010-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
The XPCSafeJSObjectWrapper class in the SafeJSObjectWrapper (aka SJOW) implementation in Mozilla Firefox 3.6.x before 3.6.9 and Thunderbird 3.1.x before 3.1.3 does not properly restrict objects at the end of scope chains, which allows remote attackers to execute arbitrary JavaScript code with chrome privileges via vectors related to a chrome privileged object and a chain ending in an outer object.

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

Mozilla Firefox and Thunderbird contain a vulnerability in the XPCSafeJSObjectWrapper (SJOW) security wrapper where scope chain access controls are improperly enforced. This allows content JavaScript to access chrome-privileged objects through a specially crafted object chain, achieving arbitrary JavaScript execution with elevated privileges.

MitigationUpgrade Mozilla Firefox to version 3.6.9 or later, and Thunderbird to version 3.1.3 or later. Alternatively, disable JavaScript or restrict browser usage to trusted sources until patching is complete.

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
ThunderbirdApplication
Affected:= 3.1= 3.1.1= 3.1.2

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

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

  1. Check Firefox installed version
    Open Firefox, type 'about:对话' in the address bar, or go to Help > About Firefox. Record the version number shown.
    Affected if Version is 3.6, 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, or 3.6.8
  2. Check Thunderbird installed version
    Open Thunderbird, go to Help > About Thunderbird. Record the version number shown.
    Affected if Version is 3.1, 3.1.1, or 3.1.2
  3. Verify JavaScript is enabled in Firefox
    In Firefox, go to Tools > Options > Content, or type 'about:preferences' and check that 'Enable JavaScript' is checked.
    Affected if JavaScript is enabled on a Firefox version matching the affected list above
  4. Verify JavaScript is enabled in Thunderbird
    In Thunderbird, go to Edit > Preferences > Advanced > Scripting, or check Tools > Options > Security > scripting, and confirm JavaScript is permitted.
    Affected if JavaScript is enabled on a Thunderbird version matching the affected list above

Your environment is affected if you are running Firefox 3.6.x (specifically 3.6, 3.6.2-3.6.4, 3.6.6-3.6.8) or Thunderbird 3.1.x (3.1, 3.1.1, 3.1.2) with JavaScript enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mozilla Firefox to version 3.6.9 or later, and Thunderbird to version 3.1.3 or later. Alternatively, disable JavaScript or restrict browser usage to trusted sources until patching is complete.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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