FirefoxWeb browser · Mozilla

CVE-2011-0076

HIGH · 7.5 CVSS v2.0 Published 2011-05-07
Fix available
A fix is available. Upgrade to after 2.0.13 or later.
See remediation →
84/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
Unspecified vulnerability in the Java Embedding Plugin (JEP) in Mozilla Firefox before 3.5.19 and 3.6.x before 3.6.17, and SeaMonkey before 2.0.14, on Mac OS X allows remote attackers to bypass intended access restrictions via unknown vectors.

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 Java Embedding Plugin (JEP) in older Mozilla Firefox (before 3.5.19 and 3.6.x before 3.6.17) and SeaMonkey (before 2.0.14) on Mac OS X contained an unspecified vulnerability allowing remote attackers to bypass intended access restrictions, likely enabling cross-origin or sandbox escapes.

MitigationUpgrade to Firefox 3.5.19+, 3.6.17+, or migrate to a modern Firefox version; similarly upgrade SeaMonkey to 2.0.14+ or use a current browser. The Java Embedding Plugin should be disabled or removed if not needed.

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.6.9= 3.6.10= 3.6.11= 3.6.12= 3.6.13
SeamonkeyApplication
Affected:<= 2.0.13= 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

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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. Confirm operating system
    Verify the system is running Mac OS X. This vulnerability only affects the Java Embedding Plugin on Mac OS X, not Windows or Linux.
    Affected if System is NOT running Mac OS X - the vulnerability does not apply
  2. Identify Firefox version
    Open Firefox, click Firefox menu > About Firefox. Record the version number. Alternatively, run 'firefox --version' in terminal.
    Affected if Version is Firefox 3.6.x (3.6, 3.6.2-3.6.13) or any version below 3.5.19 or 3.6.17
  3. Identify SeaMonkey version
    Open SeaMonkey, click SeaMonkey menu > About SeaMonkey. Record the version number. Alternatively, run 'seamonkey --version' in terminal.
    Affected if Version is SeaMonkey 2.0.x (2.0.13 or below) or SeaMonkey 1.0.x through 1.1
  4. Check for Java Embedding Plugin
    Navigate to ~/Library/Internet Plug-Ins/ or /Library/Internet Plug-Ins/ and look for files named 'JavaEmbeddingPlugin.plugin' or similar JEP components.
    Affected if The Java Embedding Plugin is present in the browser's plug-in directory
  5. Check Java plugin status
    In Firefox or SeaMonkey, go to Edit > Preferences > Applications (or Add-ons > Plugins). Look for 'Java Applet Plug-in' or 'Java Platform SE' entries.
    Affected if Java plugin is enabled in the browser

User is affected if running Mac OS X with Firefox versions below 3.5.19 or 3.6.17 (specifically 3.6.x series), or SeaMonkey 2.0.13/earlier or 1.x, AND the Java Embedding Plugin is present and Java is enabled in the browser.

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

Upgrade to Firefox 3.5.19+, 3.6.17+, or migrate to a modern Firefox version; similarly upgrade SeaMonkey to 2.0.14+ or use a current browser. The Java Embedding Plugin should be disabled or removed if not needed.

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 the upgrade done

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-2011-0076 — 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-0076 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