dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-1215

MEDIUM · 6.8 CVSS v2.0 Published 2010-07-30
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
Mozilla Firefox 3.6.x before 3.6.7 and Thunderbird 3.1.x before 3.1.1 do not properly implement access to a content object through a SafeJSObjectWrapper (aka SJOW) wrapper, which allows remote attackers to execute arbitrary JavaScript code with chrome privileges by leveraging "access to an object from the chrome scope."

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

The SafeJSObjectWrapper (SJOW) in Firefox 3.6.x before 3.6.7 and Thunderbird 3.1.x before 3.1.1 fails to properly restrict access to content objects, allowing web content JavaScript to access and manipulate chrome-scope objects. This allows remote attackers to execute arbitrary JavaScript with elevated chrome privileges.

MitigationUpgrade to Firefox 3.6.7 or later, or Thunderbird 3.1.1 or later, to obtain the patched SJOW implementation that properly enforces access restrictions between content and chrome scopes.

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.1= 3.6.2= 3.6.3= 3.6.4= 3.6.6
ThunderbirdApplication
Affected:= 3.1

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 version
    In Firefox, go to Help > About Firefox, or enter 'about:support' in the address bar, or run 'firefox --version' from command line
    Affected if The version shows 3.6.1, 3.6.2, 3.6.3, 3.6.4, or 3.6.6 (versions 3.6.7 and later are fixed)
  2. Check Thunderbird version
    In Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if The version shows 3.1.x (any version before 3.1.1 is affected; 3.1.1 and later are fixed)
  3. Confirm SJOW is in use
    The SafeJSObjectWrapper is a core JavaScript component used when web content interacts with privileged chrome objects. On Windows, the vulnerable DLL is npjp2.dll or js3250.dll in the installation directory; on Linux, libmozjs.so; on Mac, framework directory files. Inspect the installed binary versions.
    Affected if The browser uses the affected Firefox 3.6.x branch (before 3.6.7) - the SJOW component in these versions fails to enforce content/chrome scope separation

You are affected if you run Firefox 3.6.1 through 3.6.6 or Thunderbird 3.1.x before 3.1.1, as these versions contain the vulnerable SafeJSObjectWrapper that allows web content to access chrome-privileged 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.

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

Upgrade to Firefox 3.6.7 or later, or Thunderbird 3.1.1 or later, to obtain the patched SJOW implementation that properly enforces access restrictions between content and chrome scopes.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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