dbcve.org
FirefoxWeb browser · Mozilla

CVE-2006-6504

HIGH · 9.3 CVSS v2.0 Published 2006-12-20
Fix available
A fix is available. Upgrade to 1.0.7 / 1.5.0.9 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 2.x before 2.0.0.1, 1.5.x before 1.5.0.9, and SeaMonkey before 1.0.7 allows remote attackers to execute arbitrary code by appending an SVG comment DOM node to another type of document, which triggers memory corruption.

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 memory corruption vulnerability in Mozilla Firefox 2.x before 2.0.0.1, 1.5.x before 1.5.0.9, and SeaMonkey before 1.0.7 allows remote attackers to execute arbitrary code by appending an SVG comment DOM node to a non-SVG document, causing heap corruption.

MitigationUpgrade affected browsers to Firefox 2.0.0.1+, 1.5.0.9+, or SeaMonkey 1.0.7+ respectively, or migrate to supported browser versions.

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:>= 1.5, < 1.5.0.9>= 2.0, < 2.0.0.1
Ubuntu LinuxOperating system
Affected:= 5.10= 6.06= 6.10
SeamonkeyApplication
Affected:< 1.0.7

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
    Check if Mozilla Firefox or SeaMonkey is installed. In Firefox, type 'about:' in the address bar and press Enter. In SeaMonkey, go to Help > About SeaMonkey.
    Affected if The product is Firefox 1.5.x or 2.x, or SeaMonkey any version below 1.0.7
  2. Determine the exact Firefox version
    In Firefox, type 'about:' in the address bar and look for the version number displayed, or go to Help > About Firefox. Record the version (e.g., 1.5.0.8, 2.0.0.0).
    Affected if Version is 1.5.x before 1.5.0.9, or 2.x before 2.0.0.1
  3. Determine the exact SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey and record the version number.
    Affected if Version is below 1.0.7
  4. Check for JavaScript-enabled SVG rendering in non-SVG contexts
    This vulnerability is triggered when JavaScript manipulates SVG comment nodes within non-SVG HTML documents. Test by viewing a webpage containing SVG elements (such as embedded SVG graphics) in the affected browser version.
    Affected if The browser renders or processes SVG content in HTML documents while running JavaScript

The user is affected if they are running Firefox versions 1.5.0 through 1.5.0.8, Firefox 2.0.0 through 2.0.0.0, or SeaMonkey versions below 1.0.7, and if they browse webpages containing SVG content 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 1.0.7 / 1.5.0.9 / 2.0.0.1 or later
Fixed in 1.0.71.5.0.92.0.0.1
Interim mitigation

Upgrade affected browsers to Firefox 2.0.0.1+, 1.5.0.9+, or SeaMonkey 1.0.7+ respectively, or migrate to supported browser versions.

Recommended fix High confidence

Firefox 1.5.0.9 or 2.0.0.1, or SeaMonkey 1.0.7

  1. Check current Firefox or SeaMonkey version (Help > About or seamonkey -version)
  2. Download Firefox 1.5.0.9 (for 1.5.x users) or Firefox 2.0.0.1 (for 2.0.x users) from archive.mozilla.org
  3. Alternatively, download SeaMonkey 1.0.7 if using that product
  4. Close all browser windows
  5. Install the appropriate fixed version
  6. Restart the browser
  7. Verify the version shows the fixed release (1.5.0.9, 2.0.0.1, or 1.0.7)
Caveat Upgrading from Firefox 1.5/2.0 to 2.0.0.1/1.5.0.9 may break older extensions and web compatibility; consider migrating to a modern Firefox release if possible

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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