Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2004-1109: DoS via Zero-Length IP Option in Kerio Personal Firewall FWDRV.SYS

Published Dec 1, 2004 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS3.2%89th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Kerio Technologies
IdentifiersCVE-2004-1109CWE-835

A vulnerability in the FWDRV.SYS driver of Kerio Personal Firewall 4.1.1 and earlier allows remote attackers to trigger a denial of service condition. By sending specially crafted TCP, UDP, or ICMP packets with a zero-length IP Option field, an attacker can cause the driver to enter an infinite loop, resulting in excessive CPU consumption and a system freeze.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation leads to a denial of service, where the affected system becomes unresponsive due to high CPU usage and may require a manual reboot. This can be exploited remotely, impacting system availability.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, block malformed packets with zero-length IP Option fields at the network perimeter using an upstream firewall or intrusion prevention system, if possible. Monitor for abnormal traffic patterns that may indicate exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade to a version of Kerio Personal Firewall where this vulnerability is patched. If no patch is available, consider replacing the software with a supported and secure alternative.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Kerio TechnologiesPersonal Firewallapplication
FAQ

Frequently asked questions

Is CVE-2004-1109 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2004-1109 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2004-1109?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2004-1109.
Is there a patch for CVE-2004-1109?
Upgrade to a version of Kerio Personal Firewall where this vulnerability is patched. If no patch is available, consider replacing the software with a supported and secure alternative.
What products are affected by CVE-2004-1109?
Kerio Technologies Personal Firewall.
How severe is CVE-2004-1109?
CVE-2004-1109 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 3.2% (89th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.