FirefoxWeb browser · Mozilla

CVE-2006-1273

HIGH · 7.8 CVSS v2.0 Published 2006-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 1.0.7 and 1.5.0.1 allows remote attackers to cause a denial of service (crash) via an HTML tag with a large number of script action handlers such as onload and onmouseover, which triggers the crash when the user views the page source. NOTE: Red Hat has disputed this issue, suggesting that "It is likely the reporter was running the IE Tab extension," and Mozilla also confirmed that this is not an issue in Firefox itself

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

Mozilla Firefox 1.0.7 and 1.5.0.1 was reported to crash when viewing page source of HTML containing tags with a large number of script action handlers (onload, onmouseover). However, both Red Hat and Mozilla have disputed this issue, with Mozilla confirming this is not a vulnerability in Firefox itself and Red Hat suggesting the reporter may have been using the IE Tab extension.

MitigationNo remediation required for Firefox itself as this has been confirmed by Mozilla not to be a Firefox vulnerability. If encountered, ensure Firefox and all extensions are up to date.

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.7= 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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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. Check installed Firefox version
    Open Firefox, go to Help > About Mozilla Firefox, or run 'firefox -v' from command line
    Affected if Version is exactly 1.0.7 or exactly 1.5.0.1
  2. Verify if IE Tab extension is installed
    Open Firefox Add-ons Manager (Tools > Add-ons) and check for IE Tab extension
    Affected if IE Tab extension is present and was used to view the page
  3. Confirm page source viewing context
    Determine whether the crash occurred while using View > Page Source on HTML pages containing many script event handlers (onload, onmouseover)
    Affected if Page source was being viewed on HTML with unusually large numbers of script event handlers

No action needed - this issue was disputed by Mozilla and confirmed not to be a Firefox vulnerability; users should ensure Firefox and all extensions are updated to current versions.

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

No remediation required for Firefox itself as this has been confirmed by Mozilla not to be a Firefox vulnerability. If encountered, ensure Firefox and all extensions are up to date.

We can implement and validate the mitigation, then track the permanent fix — typical engagement from $1,950. Get help mitigating

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-1273 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