dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-0183

HIGH · 9.3 CVSS v2.0 Published 2010-06-24
Fix available
A fix is available. Upgrade to after 2.0.4 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
Use-after-free vulnerability in the nsCycleCollector::MarkRoots function in Mozilla Firefox 3.5.x before 3.5.10 and SeaMonkey before 2.0.5 allows remote attackers to execute arbitrary code via a crafted HTML document, related to an improper frame construction process for menus.

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

A use-after-free vulnerability exists in the nsCycleCollector::MarkRoots function in Mozilla Firefox 3.5.x before 3.5.10 and SeaMonkey before 2.0.5. The flaw stems from improper frame construction during menu processing, allowing an attacker to free memory that the code still references, leading to arbitrary code execution when a crafted HTML document triggers the condition.

MitigationUpgrade affected Firefox installations to version 3.5.10 or later, and SeaMonkey to version 2.0.5 or later. Alternatively, disable JavaScript or restrict execution of untrusted HTML content until patching can be completed.

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.5.9
SeamonkeyApplication
Affected:<= 2.0.4= 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. Identify the installed browser product
    Open the browser and look at the application name in the title bar or window chrome. This CVE affects either Mozilla Firefox or SeaMonkey.
    Affected if The product is Firefox version 3.5.x (3.5 through 3.5.9) or SeaMonkey version 1.x (1.0 through 1.1) or SeaMonkey version 2.0.4 or earlier.
  2. Determine the exact Firefox version
    In Firefox, click Help > About Firefox (or on Linux, run firefox --version). The version dialog displays the full version number.
    Affected if The version starts with 3.5 and the minor version is 0 through 9 (e.g., 3.5.0, 3.5.1, 3.5.7, 3.5.9). Version 3.5.8 and 3.5.10 are not listed as affected in this CVE.
  3. Determine the exact SeaMonkey version
    In SeaMonkey, click Help > About SeaMonkey. The version dialog displays the full version number.
    Affected if The version is 2.0.4 or lower, or any 1.x version from 1.0 through 1.1.
  4. Verify JavaScript is enabled (required for exploitation)
    In Firefox: Tools > Options > Content (check 'Enable JavaScript'). In SeaMonkey: Edit > Preferences > Advanced > Scripts & Plugins. This is the default enabled state.
    Affected if JavaScript is enabled in the browser. The vulnerability exists in the core code but requires JavaScript to be active to trigger the use-after-free condition.

A user is affected if they are running Mozilla Firefox version 3.5.0 through 3.5.9, or SeaMonkey version 1.0 through 1.1, or SeaMonkey version 2.0.4 or earlier, with JavaScript enabled.

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

Upgrade affected Firefox installations to version 3.5.10 or later, and SeaMonkey to version 2.0.5 or later. Alternatively, disable JavaScript or restrict execution of untrusted HTML content until patching can be completed.

Recommended fix High confidence

Firefox 3.5.10 or SeaMonkey 2.0.5 (or migrate to a currently supported browser)

  1. 1. Save any open work and close all browser instances
  2. 2. Download Firefox 3.5.10 from the Mozilla archives or a trusted mirror
  3. 3. Run the installer and follow the prompts to upgrade
  4. 4. After installation, verify the version by navigating to Help > About Firefox
  5. 5. Alternatively, upgrade to a currently supported Firefox release (ESR 115 or later) for continued security updates
  6. 6. For SeaMonkey users, upgrade to SeaMonkey 2.0.5 or later, or migrate to a supported browser
Caveat Firefox 3.5.x and SeaMonkey 1.x/2.0.x are end-of-life and no longer receive security patches; upgrading may require迁移 to newer browser versions with different UI/extensions

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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