dbcve.org
FirefoxWeb browser · Mozilla

CVE-2006-0297

MEDIUM · 5.1 CVSS v2.0 Published 2006-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Multiple integer overflows in Mozilla Firefox 1.5, Thunderbird 1.5 if Javascript is enabled in mail, and SeaMonkey before 1.0 might allow remote attackers to execute arbitrary code via the (1) EscapeAttributeValue in jsxml.c for E4X, (2) nsSVGCairoSurface::Init in SVG, and (3) nsCanvasRenderingContext2D.cpp in Canvas.

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

Integer overflow vulnerabilities in Mozilla Firefox 1.5, Thunderbird 1.5, and SeaMonkey before 1.0 exist in three locations: EscapeAttributeValue (jsxml.c for E4X), nsSVGCairoSurface::Init (SVG rendering), and nsCanvasRenderingContext2D.cpp (Canvas). These overflows can be exploited by malicious web pages or emails to execute arbitrary code via heap corruption or buffer overflows.

MitigationUpgrade to Firefox 1.5.0.1+, Thunderbird 1.5.0.1+, or SeaMonkey 1.0+. For Thunderbird, also disable Javascript in mail settings to reduce attack surface until patching is complete.

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
SeamonkeyApplication
Affected:= 1.0
ThunderbirdApplication
Affected:= 1.5

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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/Au:N/C:P/I:P/A:P

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 product and version
    Open the application and navigate to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey. Alternatively, check the application executable version property.
    Affected if Version is Firefox 1.5, Thunderbird 1.5, or SeaMonkey versions before 1.0
  2. Check if E4X (ECMAScript for XML) support is enabled in Firefox
    In Firefox address bar, type about:config and search for 'xml.script.enabled' or 'javascript.options.xml.ecma'. These flags control E4X functionality.
    Affected if E4X is enabled (value set to true) on an affected Firefox version
  3. Check if SVG rendering is enabled in Firefox or SeaMonkey
    In Firefox address bar, type about:config and search for 'svg.enabled' or check if the application renders SVG content. Visit a test page with inline SVG to confirm rendering works.
    Affected if SVG rendering is functional on an affected version
  4. Check if Canvas 2D rendering is enabled
    In Firefox address bar, type about:config and search for 'html5.canvas.enabled'. Visit a web page that uses HTML5 Canvas to confirm functionality.
    Affected if Canvas feature is enabled and functional on an affected version
  5. Confirm Thunderbird email Javascript setting
    In Thunderbird, go to Edit > Preferences > Security and check if 'Enable Javascript' is allowed in mail messages. Also check Edit > Preferences > Advanced > Config Editor for 'javascript.enabled'.
    Affected if Javascript is enabled in Thunderbird 1.5, allowing malicious emails to trigger the vulnerability

You are affected if you are running Firefox 1.5, Thunderbird 1.5, or SeaMonkey before 1.0, and any of the affected features (E4X, SVG rendering, or Canvas) are enabled on your installation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Firefox 1.5.0.1+, Thunderbird 1.5.0.1+, or SeaMonkey 1.0+. For Thunderbird, also disable Javascript in mail settings to reduce attack surface until patching is complete.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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