FirefoxWeb browser · Mozilla

CVE-2006-6502

HIGH · 7.1 CVSS v2.0 Published 2006-12-20

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

80/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Use-after-free vulnerability in the LiveConnect bridge code for Mozilla Firefox 2.x before 2.0.0.1, 1.5.x before 1.5.0.9, Thunderbird before 1.5.0.9, and SeaMonkey before 1.0.7 allows remote attackers to cause a denial of service (crash) via unknown vectors.

Technical summary

dbcve analysis · moderate confidence

Use-after-free vulnerability in LiveConnect bridge code (Java/JS integration) allows remote attackers to cause denial of service via memory corruption. The vulnerability stems from improper memory management when handling LiveConnect objects, leading todangling pointer dereference.

MitigationUpdate to patched versions: Firefox 2.0.0.1+, Firefox 1.5.0.9+, Thunderbird 1.5.0.9+, or SeaMonkey 1.0.7+. This is a straightforward version upgrade with no code changes required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:= 1.5= 1.5.0.1= 1.5.0.2= 1.5.0.3= 1.5.0.4= 1.5.0.5= 1.5.0.6= 1.5.0.7= 1.5.0.8= 2.0

SeamonkeyApplication

Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6

ThunderbirdApplication

Affected:= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8= 0.9

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: None
Integrity: None
Availability: Complete

AV:N/AC:M/Au:N/C:N/I:N/A:C

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the installed Mozilla product

Check which Mozilla application is installed: Firefox, SeaMonkey, or Thunderbird. This can be done via the application's Help > About menu, or by checking the executable name and properties.

Affected if Any of the three products (Firefox, SeaMonkey, Thunderbird) is installed
Determine the installed version number

Access Help > About in the application menu, or run the executable with --version flag if available, or check the program files directory for version metadata.

Affected if The version matches any of the affected versions listed for that product
Compare against affected version list

For Firefox: versions 1.5, 1.5.0.1 through 1.5.0.8, and 2.0 are affected. For SeaMonkey: versions 1.0, 1.0.1 through 1.0.6 are affected. For Thunderbird: versions 0.1 through 0.9 are affected.

Affected if The installed version exactly matches one of the listed affected versions (note: Thunderbird 0.1 through 0.9 are all affected; Firefox 1.5.x series and 2.0; SeaMonkey 1.0.x series)

If the installed Mozilla product version exactly matches one of the versions listed in the affected products (Firefox 1.5, 1.5.0.1-1.5.0.8, or 2.0; SeaMonkey 1.0-1.0.6; Thunderbird 0.1-0.9), the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to patched versions: Firefox 2.0.0.1+, Firefox 1.5.0.9+, Thunderbird 1.5.0.9+, or SeaMonkey 1.0.7+. This is a straightforward version upgrade with no code changes required.

Fix this in Firefox Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

5.0 hours of engineering $860

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-6502 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-6502?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.1 High

Exploit likelihood EPSS, next 30 days 2.4%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 5 hrs · Low

Typical engagement from $860

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2006-6502 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References