dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-3772

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 calculate index values for certain child content in a XUL tree, which allows remote attackers to execute arbitrary code via vectors involving a DIV element within a treechildren element.

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

Memory corruption vulnerability in Mozilla Firefox and SeaMonkey's XUL tree implementation where improper index calculation for child content allows remote arbitrary code execution via a specially crafted DIV element within a treechildren element.

MitigationUpgrade to Firefox 3.5.16/3.6.13 or later, or SeaMonkey 2.0.11 or later. If using XUL in custom applications, validate and bounds-check index calculations when processing child elements.

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. Identify installed Mozilla browser product
    Check for Firefox or SeaMonkey executables. On Windows: look in Program Files for 'Mozilla Firefox' or 'SeaMonkey' folders. On Linux: check /usr/bin/firefox or /usr/bin/seamonkey. On Mac: check /Applications/Firefox.app or /Applications/SeaMonkey.app
    Affected if Neither Firefox nor SeaMonkey is installed, then this CVE does not apply to your environment
  2. Determine Firefox version
    For Firefox: Run 'firefox --version' from command line, or open Firefox, go to Help > About Firefox. Look for version number such as 3.6.x or 3.5.x
    Affected if Version is 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, or any 3.5.x version up to and including 3.5.15
  3. Determine SeaMonkey version
    For SeaMonkey: Run 'seamonkey --version' from command line, or open SeaMonkey, go to Help > About SeaMonkey. Look for version number such as 1.x or 2.0.x
    Affected if Version is 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, or any 2.0.x version up to and including 2.0.10
  4. Check for XUL tree usage in custom applications
    If you have custom applications using XUL (not the browser itself), search source code for '<tree>' or '<treechildren>' XML elements. Also search for any JavaScript code that manipulates XUL tree child indices programmatically
    Affected if Custom application uses XUL tree elements and processes child elements with index calculations that could overflow

You are affected if you run Firefox versions 3.5.x through 3.5.15 or 3.6.x through 3.6.12, or SeaMonkey versions 1.0.x through 1.1 or 2.0.x through 2.0.10, and utilize XUL tree functionality where a crafted DIV element within a treechildren element could be processed.

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 to Firefox 3.5.16/3.6.13 or later, or SeaMonkey 2.0.11 or later. If using XUL in custom applications, validate and bounds-check index calculations when processing child elements.

Recommended fix High confidence

Firefox 3.6.13+ (or migrate to modern Firefox ESR/current stable); SeaMonkey 2.0.11+

  1. 1. Back up any important bookmarks, passwords, and personal data from the current browser profile.
  2. 2. Download Firefox 3.6.13 or later (preferably a modern Firefox release such as Firefox ESR or current stable version).
  3. 3. Download SeaMonkey 2.0.11 or later (preferably a modern release).
  4. 4. Install the new browser version over the existing installation, or to a new directory.
  5. 5. Verify the installed version by checking Help > About Firefox or About SeaMonkey.
  6. 6. Restore user data from the backup or migrate to the new profile format.
Caveat Upgrading from Firefox 3.6.x (2010) to 3.6.13 or newer will likely break legacy extensions and plugins; consider migrating to a modern Firefox version for continued security support

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
  • 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-3772 — 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-3772 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