dbcve.org
FirefoxWeb browser · Mozilla

CVE-2006-1728

HIGH · 9.3 CVSS v2.0 Published 2006-04-14
Fix available
A fix is available. Upgrade to 1.0.1 / 1.0.8 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
Unspecified vulnerability in 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 unknown vectors related to the crypto.generateCRMFRequest method.

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 vulnerability in the crypto.generateCRMFRequest method in Mozilla Firefox, Thunderbird, Mozilla Suite, and SeaMonkey allows remote attackers to execute arbitrary code via unspecified vectors. The CVSS 9.3 score indicates critical severity with complete compromise of confidentiality, integrity, and availability.

MitigationUpgrade to Firefox 1.5.0.2/1.0.8, Thunderbird 1.5.0.2/1.0.8, Mozilla Suite 1.7.13, or SeaMonkey 1.0.1 or later. If these legacy applications cannot be updated, consider replacing them with supported modern alternatives.

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.8>= 1.5, < 1.5.0.2
Ubuntu LinuxOperating system
Affected:= 4.10= 5.04= 5.10
Mozilla SuiteApplication
Affected:< 1.7.13
SeamonkeyApplication
Affected:< 1.0.1
ThunderbirdApplication
Affected:>= 1.0, < 1.0.8>= 1.5, < 1.5.0.2

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. Check Firefox version
    Open Firefox, go to Help > About Mozilla Firefox, or run 'firefox -v' from command line. Note the version number displayed.
    Affected if Version is 1.0 through 1.0.7, or 1.5.0.0 through 1.5.0.1 (i.e., >= 1.0 and < 1.0.8, or >= 1.5 and < 1.5.0.2)
  2. Check Thunderbird version
    Open Thunderbird, go to Help > About Thunderbird, or run 'thunderbird -v' from command line. Note the version number displayed.
    Affected if Version is 1.0 through 1.0.7, or 1.5.0.0 through 1.5.0.1 (i.e., >= 1.0 and < 1.0.8, or >= 1.5 and < 1.5.0.2)
  3. Check SeaMonkey version
    Open SeaMonkey, go to Help > About SeaMonkey. Note the version number displayed.
    Affected if Version is any release prior to 1.0.1 (i.e., < 1.0.1)
  4. Check Mozilla Suite version
    Open Mozilla Suite, go to Help > About Mozilla Suite. Note the version number displayed.
    Affected if Version is any release prior to 1.7.13 (i.e., < 1.7.13)

If any of these Mozilla products are installed and their installed version falls within the vulnerable ranges listed above, the environment is affected by CVE-2006-1728.

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.1 / 1.0.8 / 1.5.0.2 or later
Fixed in 1.0.11.0.81.5.0.2
Interim mitigation

Upgrade to Firefox 1.5.0.2/1.0.8, Thunderbird 1.5.0.2/1.0.8, Mozilla Suite 1.7.13, or SeaMonkey 1.0.1 or later. If these legacy applications cannot be updated, consider replacing them with supported modern alternatives.

Recommended fix High confidence

Firefox 1.0.8 / 1.5.0.2; Thunderbird 1.0.8 / 1.5.0.2; Mozilla Suite 1.7.13; SeaMonkey 1.0.1

  1. Upgrade Firefox 1.0.x to version 1.0.8 or later, or migrate to a supported modern Firefox version
  2. Upgrade Firefox 1.5.x to version 1.5.0.2 or later, or migrate to a supported modern Firefox version
  3. Upgrade Thunderbird 1.0.x to version 1.0.8 or later, or migrate to a supported modern Thunderbird version
  4. Upgrade Thunderbird 1.5.x to version 1.5.0.2 or later, or migrate to a supported modern Thunderbird version
  5. Upgrade Mozilla Suite to version 1.7.13 or later, or migrate to SeaMonkey which replaced it
  6. Upgrade SeaMonkey to version 1.0.1 or later
  7. For Ubuntu systems (4.10, 5.04, 5.10), apply vendor security updates or upgrade to a supported Ubuntu release
Caveat These are very old (2006) versions. The products and Ubuntu releases listed are obsolete and no longer receive security updates. Upgrading to modern supported versions is strongly recommended as these legacy versions may have compatibility issues with current web standards and protocols.

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 the upgrade done

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-1728 — 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-1728 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