FirefoxWeb browser · Mozilla

CVE-2011-3666

MEDIUM · 6.8 CVSS v2.0 Published 2011-12-21
Fix available
A fix is available. Upgrade to after 3.6.24 or later.
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 before 3.6.25 and Thunderbird before 3.1.17 on Mac OS X do not consider .jar files to be executable files, which allows user-assisted remote attackers to bypass intended access restrictions via a crafted file. NOTE: this vulnerability exists because of an incorrect fix for CVE-2011-2372 on Mac OS X.

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

Firefox and Thunderbird on Mac OS X prior to versions 3.6.25 and 3.1.17 respectively fail to treat .jar (Java Archive) files as executable files, allowing security restrictions to be bypassed. This stems from an incorrect fix for CVE-2011-2372. The vulnerability is user-assisted, requiring the victim to interact with a crafted file.

MitigationUpgrade Firefox to version 3.6.25 or later and Thunderbird to version 3.1.17 or later on Mac OS X systems. Alternatively, disable Java plugin execution in the browser as a defense-in-depth measure.

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.24= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
ThunderbirdApplication
Affected:<= 3.1.16= 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
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. Identify installed Mozilla product
    Open terminal and run: ps -ax | grep -iE 'firefox|thunderbird' or check /Applications folder for Firefox or Thunderbird
    Affected if Neither Firefox nor Thunderbird is installed (not affected)
  2. Determine Firefox version
    For Firefox: click Firefox menu > About Firefox, or run: /Applications/Firefox.app/Contents/MacOS/firefox -version
    Affected if Version is 3.6.24 or earlier, or one of 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, 0.9 (affected)
  3. Determine Thunderbird version
    For Thunderbird: click Thunderbird menu > About Thunderbird, or run: /Applications/Thunderbird.app/Contents/MacOS/thunderbird -version
    Affected if Version is 3.1.16 or earlier, or one of 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 (affected)
  4. Confirm Mac OS X environment
    Run: uname -a or click Apple menu > About This Mac
    Affected if Operating system is not Mac OS X (not affected)
  5. Check if Java plugin is present
    In Firefox: go to Add-ons > Plugins; in Thunderbird: go to Tools > Add-ons > Plugins; look for Java plugin entry
    Affected if Java plugin is disabled or not installed (the JAR bypass does not apply, though the code flaw may still exist)

User is affected if they have Firefox <= 3.6.24 (or older version 0.1-0.9) or Thunderbird <= 3.1.16 (or older version 0.1-0.8) running on Mac OS X, with Java plugin enabled, and they can be tricked into interacting with a crafted .jar file.

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

Upgrade Firefox to version 3.6.25 or later and Thunderbird to version 3.1.17 or later on Mac OS X systems. Alternatively, disable Java plugin execution in the browser as a defense-in-depth measure.

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3666 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3666 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