dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-3775

HIGH · 9.3 CVSS v2.0 Published 2010-12-10
Fix available
A fix is available. Upgrade to after 3.5.15 or later.
See remediation →
100/100
Remediation priority · Urgent
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.5.16 and 3.6.x before 3.6.13, and SeaMonkey before 2.0.11, does not properly handle certain redirections involving data: URLs and Java LiveConnect scripts, which allows remote attackers to start processes, read arbitrary local files, and establish network connections via vectors involving a refresh value in the http-equiv attribute of a META element, which causes the wrong security principal to be used.

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

Cross-origin vulnerability in Mozilla Firefox and SeaMonkey where META refresh redirections to data: URLs and Java LiveConnect scripts use the wrong security principal. This allows remote attackers to read arbitrary local files, start processes, and establish network connections by exploiting the http-equiv refresh attribute.

MitigationUpgrade Firefox to version 3.5.16/3.6.13 or later, or SeaMonkey to 2.0.11 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.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.5.15
SeamonkeyApplication
Affected:<= 2.0.10= 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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. Determine installed Firefox version
    In Firefox, go to Help > About Firefox, or navigate to about:support in the address bar. The version is displayed at the top of the page.
    Affected if The version is 3.5.x and <= 3.5.15, or is 3.6.x and one of: 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, or 3.6.12.
  2. Determine installed SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey. The version is displayed in the dialog that opens.
    Affected if The version is 1.0.x through 1.1.x inclusive, or is 2.0.x and <= 2.0.10.
  3. Confirm Java plugin is enabled
    In Firefox, type about:plugins in the address bar and look for Java (TM) Platform SE entry. In SeaMonkey, check via Tools > Options > Advanced > Java. The Java plugin must be enabled for the LiveConnect portion of this vulnerability.
    Affected if Java plugin is enabled and the browser version is within the affected ranges.
  4. Check for META refresh usage with external content
    Review any locally hosted or trusted web pages that contain <meta http-equiv="refresh"> tags. Specifically inspect whether any such tags redirect to data: URLs (data:text/html,...) or load Java applets.
    Affected if Pages use META refresh with data: URLs or load Java applets via this mechanism, and the browser is an affected version.

You are affected if you run Firefox version 3.5.x through 3.5.15 or 3.6.x through 3.6.12, or SeaMonkey 1.0.x through 1.1.x or 2.0.x through 2.0.10, and you have Java enabled or visit pages with META refresh to data: URLs.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.5.15
Interim mitigation

Upgrade Firefox to version 3.5.16/3.6.13 or later, or SeaMonkey to 2.0.11 or later.

Recommended fix High confidence

Firefox 3.6.13 or later, or SeaMonkey 2.0.11 or later

  1. 1. Determine the currently installed browser version (Firefox or SeaMonkey) by checking About in the application menu
  2. 2. Back up important user data (bookmarks, passwords, saved forms) from the browser profile directory
  3. 3. For Firefox users: Download and install Firefox 3.6.13 or later from the Mozilla archives
  4. 4. For SeaMonkey users: Download and install SeaMonkey 2.0.11 or later from the SeaMonkey archives
  5. 5. After installation, verify the version by checking the About dialog
  6. 6. Test that previously used web applications and websites function correctly
  7. 7. Restore user data from the backup if needed
Caveat These are very old browser versions from 2010; modern websites and web applications may not function properly; consider migrating to a modern supported browser version for full functionality and continued security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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