dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-1209

HIGH · 9.3 CVSS v2.0 Published 2010-07-30
Fix available
A fix is available. Upgrade to after 2.0.5 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 NodeIterator implementation in Mozilla Firefox 3.5.x before 3.5.11 and 3.6.x before 3.6.7, and SeaMonkey before 2.0.6, allows remote attackers to execute arbitrary code via a crafted NodeFilter that detaches DOM nodes, related to the NodeIterator interface and a javascript callback.

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 NodeIterator implementation of Firefox 3.5.x before 3.5.11 and 3.6.x before 3.6.7, as well as SeaMonkey before 2.0.6. The flaw is triggered when a crafted NodeFilter containing a JavaScript callback detaches DOM nodes during iteration, causing the NodeIterator to reference freed memory and enabling arbitrary code execution.

MitigationUpdate affected installations to Firefox 3.5.11/3.6.7 or later, SeaMonkey 2.0.6 or later, or migrate to a supported browser version. Alternatively, disable JavaScript as a temporary workaround until patching is feasible.

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.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.5.7= 3.5.9= 3.5.10= 3.6.1= 3.6.2= 3.6.3
SeamonkeyApplication
Affected:<= 2.0.5= 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 installed browser product
    Check whether Mozilla Firefox or SeaMonkey is installed by looking for the application in the system program directory or by typing 'firefox -v' or 'seamonkey -v' in the command line
    Affected if Either Firefox or SeaMonkey is installed and the version falls within the affected ranges
  2. Determine Firefox version
    Run 'firefox -v' or 'firefox --version' from command line, or access Help > About Firefox in the browser menu
    Affected if Version is 3.5.1 through 3.5.10, or 3.6.1 through 3.6.3 (any version below 3.5.11 or below 3.6.7 in those branches)
  3. Determine SeaMonkey version
    Run 'seamonkey -v' or 'seamonkey --version' from command line, or access Help > About SeaMonkey in the browser menu
    Affected if Version is 1.0.x through 1.1.x, or 2.0.5 or earlier (any version below 2.0.6)
  4. Compare version to fixed releases
    If Firefox 3.5.x is found, confirm it is below 3.5.11. If Firefox 3.6.x is found, confirm it is below 3.6.7. If SeaMonkey 1.x is found, any version is affected. If SeaMonkey 2.x is found, confirm it is below 2.0.6
    Affected if The installed version matches any of the affected version ranges listed in the CVE

A user is affected if they have Firefox 3.5.x before 3.5.11, Firefox 3.6.x before 3.6.7, SeaMonkey 1.x any version, or SeaMonkey 2.x before 2.0.6 installed and use the browser 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.5
Interim mitigation

Update affected installations to Firefox 3.5.11/3.6.7 or later, SeaMonkey 2.0.6 or later, or migrate to a supported browser version. Alternatively, disable JavaScript as a temporary workaround until patching is feasible.

Recommended fix High confidence

Firefox 3.5.11 / 3.6.7 or later; SeaMonkey 2.0.6 or later

  1. Download and install Firefox 3.5.11 or later (or preferably Firefox 3.6.7+) from mozilla.org
  2. For SeaMonkey users, download and install SeaMonkey 2.0.6 or later from mozilla.org
  3. After upgrading, verify the browser version by navigating to Help > About to confirm the installed version
  4. Alternatively, upgrade to a modern supported version of Firefox (current stable release) for continued security support
Caveat These are very old browser versions from 2010; upgrading to modern Firefox may require migrating bookmarks, extensions, and settings; some legacy web applications may not be compatible with modern browsers

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-1209 — 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-1209 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