dbcve.org
FirefoxWeb browser · Mozilla

CVE-2006-0748

HIGH · 9.3 CVSS v2.0 Published 2006-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 and Thunderbird 1.x before 1.5.0.2 and 1.0.x before 1.0.8, Mozilla Suite before 1.7.13, and SeaMonkey before 1.0.1 allows remote attackers to execute arbitrary code via "an invalid and non-sensical ordering of table-related tags" that results in a negative array index.

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 remote code execution vulnerability in Mozilla Firefox, Thunderbird, and SeaMonkey where malformed table HTML tags cause a negative array index during rendering, leading to memory corruption that can be exploited to execute arbitrary code.

MitigationUpdate to patched versions (Firefox 1.5.0.2+/1.0.8+, Mozilla Suite 1.7.13+, SeaMonkey 1.0.1+) or later. If patching is not feasible, disable JavaScript and restrict access to untrusted websites.

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.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.5= 1.5.0.1= preview_release
SeamonkeyApplication
Affected:= 1.0
ThunderbirdApplication
Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.5= 1.5.0.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 Mozilla product
    Open a terminal or command prompt and run: on Windows, check Start Menu for product name or run 'reg query "HKLM\SOFTWARE\Mozilla\Mozilla Firefox"' or similar for Thunderbird/SeaMonkey; on Linux, run 'dpkg -l | grep -i mozilla' or 'rpm -qa | grep -i mozilla'; on macOS, check /Applications folder for Firefox, Thunderbird, or SeaMonkey
    Affected if The installed product is Firefox, Thunderbird, or SeaMonkey (any of these three)
  2. Determine the exact version number
    Run the product and navigate to Help > About, or from command line: on Windows use '"C:\Program Files\Mozilla Firefox\firefox.exe" -v' (adjust path as needed); on Linux use 'firefox --version' or 'thunderbird --version' or 'seamonkey --version'
    Affected if Version output is any of: Firefox 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.5, 1.5.0.1, or preview_release; SeaMonkey 1.0; Thunderbird 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.5, or 1.5.0.1
  3. Verify if the vulnerability is exploitable
    Confirm that the product's HTML rendering engine is enabled: for Firefox/SeaMonkey, ensure JavaScript and HTML rendering are not disabled via preferences or about:config; for Thunderbird, ensure HTML email rendering is enabled in preferences under 'Composition' or 'Display'
    Affected if The HTML rendering engine is active and untrusted web content or HTML emails can be loaded, since the flaw triggers during table tag rendering

You are affected if you have Firefox 1.0.x through 1.5.0.1, SeaMonkey 1.0, or Thunderbird 1.0.x through 1.5.0.1 with HTML rendering enabled, as these versions contain the flawed table rendering code that can be triggered by malformed HTML tables.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to patched versions (Firefox 1.5.0.2+/1.0.8+, Mozilla Suite 1.7.13+, SeaMonkey 1.0.1+) or later. If patching is not feasible, disable JavaScript and restrict access to untrusted websites.

Recommended fix High confidence

For Firefox 1.0.x: upgrade to Firefox 1.0.8 or later (or modern Firefox ESR); For Firefox 1.5.x: upgrade to Firefox 1.5.0.2 or later; For Thunderbird 1.0.x: upgrade to Thunderbird 1.0.8 or later; For SeaMonkey 1.0: upgrade to SeaMonkey 1.0.1 or later

  1. 1. Identify the currently installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) and its exact version.
  2. 2. For Firefox 1.0.x users: Uninstall Firefox 1.0.x and install Firefox 1.0.8 or later, or preferably a more recent supported version.
  3. 3. For Firefox 1.x (1.5.x) users: Upgrade to Firefox 1.5.0.2 or later, or preferably a more recent supported version.
  4. 4. For Thunderbird 1.0.x users: Uninstall Thunderbird 1.0.x and install Thunderbird 1.0.8 or later, or preferably a more recent supported version.
  5. 5. For SeaMonkey 1.0 users: Uninstall SeaMonkey 1.0 and install SeaMonkey 1.0.1 or later, or preferably a more recent supported version.
  6. 6. After upgrading, verify the new version by checking Help > About [Product Name].
  7. 7. Ensure any browser plugins or extensions are compatible with the new version or updated accordingly.
Caveat These are very old 2006-era products. Upgrading may require migration to significantly newer versions, potentially affecting user preferences, add-ons, and legacy plugin compatibility. Consider migrating to modern supported versions (Firefox ESR, Thunderbird ESR) for ongoing security updates.

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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