FirefoxWeb browser · Mozilla

CVE-2010-0178

HIGH · 7.6 CVSS v2.0 Published 2010-04-05
Fix available
A fix is available. Upgrade to after 3.0.17 or later.
See remediation →
85/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.0.19, 3.5.x before 3.5.9, and 3.6.x before 3.6.2, and SeaMonkey before 2.0.4, does not prevent applets from interpreting mouse clicks as drag-and-drop actions, which allows remote attackers to execute arbitrary JavaScript with Chrome privileges by loading a chrome: URL and then loading a javascript: URL.

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

This browser vulnerability allows malicious web pages to execute arbitrary JavaScript with Chrome privileges by exploiting how applets interpret mouse clicks as drag-and-drop actions, chaining chrome: and javascript: URL loads to bypass security restrictions.

MitigationUpgrade affected Mozilla products to Firefox 3.0.19, 3.5.9, 3.6.2 or later, or SeaMonkey 2.0.4 or later.

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.5= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.5.7= 3.6<= 3.0.17= 0.1= 0.2
SeamonkeyApplication
Affected:<= 2.0.3= 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
High
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/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 the installed Mozilla product
    Open the application and go to Help > About (Firefox or SeaMonkey). Alternatively, check the application executable or registry entry for the product name.
    Affected if The product is either Mozilla Firefox or Mozilla SeaMonkey
  2. Determine Firefox version number
    In Firefox, go to Help > About Firefox. The version displayed (e.g., 3.5.7, 3.6, 3.0.17) is the installed version.
    Affected if The version matches any of: 3.5.x (3.5.1 through 3.5.7), 3.6, 3.0.x (any version up to and including 3.0.17), or legacy versions 0.1 or 0.2
  3. Determine SeaMonkey version number
    In SeaMonkey, go to Help > About SeaMonkey. The version displayed (e.g., 2.0.3, 1.1.19) is the installed version.
    Affected if The version matches any of: 2.0.x (any version up to and including 2.0.3), or 1.x versions (1.0 through 1.1)
  4. Verify Java plugin is enabled
    Check Firefox/SeaMonkey Add-ons > Plugins section. Look for 'Java Platform SE' or similar Java plugin entry.
    Affected if The Java plugin is installed and enabled (the vulnerability exploits applet drag-and-drop behavior)

You are affected if you are running Firefox version 3.5.x, 3.6, 3.0.x through 3.0.17, or SeaMonkey 2.0.3 or earlier, and the Java plugin is enabled to handle applets.

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.0.17
Interim mitigation

Upgrade affected Mozilla products to Firefox 3.0.19, 3.5.9, 3.6.2 or later, or SeaMonkey 2.0.4 or later.

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-2010-0178 — 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-2010-0178 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