FirefoxWeb browser · Mozilla

CVE-2007-3845

HIGH · 9.3 CVSS v2.0 Published 2007-08-08

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

NVD · unedited

Mozilla Firefox before 2.0.0.6, Thunderbird before 1.5.0.13 and 2.x before 2.0.0.6, and SeaMonkey before 1.1.4 allow remote attackers to execute arbitrary commands via certain vectors associated with launching "a file handling program based on the file extension at the end of the URI," a variant of CVE-2007-4041. NOTE: the vendor states that "it is still possible to launch a filetype handler based on extension rather than the registered protocol handler."

Technical summary

dbcve analysis · high confidence

This is a URI handling vulnerability in older Mozilla products (Firefox <2.0.0.6, Thunderbird <1.5.0.13/2.0.0.6, SeaMonkey <1.1.4) where maliciously crafted URIs can trigger the browser to launch external file-type handlers based on file extension parsing rather than proper protocol handler registration, enabling arbitrary command execution.

MitigationUpgrade to Firefox 2.0.0.6, Thunderbird 1.5.0.13/2.0.0.6, SeaMonkey 1.1.4 or later versions. If upgrading is not possible, disable or restrict the ability for browsers to launch external handlers and consider using a modern browser.

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:= 2.0.0.5

SeamonkeyApplication

Affected:= 1.1.3

ThunderbirdApplication

Affected:= 2.0.0.5

CVSS breakdown

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?

dbcve checks

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

Identify installed Mozilla product

Open the application and navigate to Help > About [Product Name] to view the exact version number, or run: 'firefox --version', 'thunderbird --version', or 'seamonkey --version' from command line

Affected if The product is Firefox, Thunderbird, or SeaMonkey and the version matches the affected versions below
Check Firefox version

In Firefox, go to Help > About Firefox, or run 'firefox --version'

Affected if Version is exactly 2.0.0.5 (or any version below 2.0.0.6 in the 2.x line)
Check Thunderbird version

In Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version'

Affected if Version is exactly 2.0.0.5 (or any version below 2.0.0.6 in the 2.x line, or below 1.5.0.13 in the 1.5 line)
Check SeaMonkey version

In SeaMonkey, go to Help > About SeaMonkey, or run 'seamonkey --version'

Affected if Version is exactly 1.1.3 (or any version below 1.1.4 in the 1.x line)

You are affected if you have Firefox 2.0.0.5, Thunderbird 2.0.0.5, or SeaMonkey 1.1.3, or any older version in those product lines prior to the fixed releases (Firefox 2.0.0.6, Thunderbird 1.5.0.13/2.0.0.6, SeaMonkey 1.1.4)

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to Firefox 2.0.0.6, Thunderbird 1.5.0.13/2.0.0.6, SeaMonkey 1.1.4 or later versions. If upgrading is not possible, disable or restrict the ability for browsers to launch external handlers and consider using a modern browser.

Recommended fix High confidence

Firefox 2.0.0.6+, SeaMonkey 1.1.4+, Thunderbird 1.5.0.13+/2.0.0.6+

Upgrade Firefox to version 2.0.0.6 or later
Upgrade SeaMonkey to version 1.1.4 or later
Upgrade Thunderbird to version 1.5.0.13, 2.0.0.6, or later

Caveat These are legacy product versions from 2007; upgrading may require migration to supported branches (e.g., Firefox 3.x+)

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

Fix this in Firefox Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $890

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2007-3845 — 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-2007-3845 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2007-3845?

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 9.3 High

Exploit likelihood EPSS, next 30 days 5.7%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2007-3845 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