Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2008-4609: Sockstress TCP Connection Queue Exhaustion DoS

Published Oct 20, 2008 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.1High · v2
EPSS32.4%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
BsdBsdiCisco SystemsDragonFly BSDFreebsdLinuxMidnightbsdNetbsd
IdentifiersCVE-2008-4609CWE-400

CVE-2008-4609 is a denial-of-service vulnerability affecting TCP implementations in multiple operating systems and network products, including Linux, BSD-derived platforms, Microsoft Windows, Cisco products, and likely other TCP/IP stacks. The issue is associated with the Sockstress class of attacks, in which a remote attacker establishes large numbers of TCP connections and manipulates TCP state information—particularly through zero-window advertisements and related persist-condition behavior—to keep connections alive while consuming disproportionate kernel and application resources. By forcing the target to retain state for many attacker-controlled connections without completing normal data flow, the attacker can exhaust connection queues and other per-connection resources.

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 allows a remote, unauthenticated attacker to cause denial of service by exhausting TCP connection handling resources such as connection queue entries, TCP state table capacity, buffers, and potentially application memory associated with stalled connections. This can prevent legitimate clients from establishing or maintaining connections and may render affected services, or in some cases the host networking stack, unresponsive for the duration of the attack.

Mitigation

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

Limit exposure of TCP services to untrusted networks using firewalls, ACLs, or upstream filtering. Where supported, tune TCP stack behavior to more aggressively terminate suspicious or long-lived persist-condition connections and enforce resource limits on stalled sessions, while validating that such changes do not disrupt legitimate traffic. Prioritize protection for Internet-facing services and apply any vendor-specific hardening guidance for handling zero-window or abnormal TCP state abuse.

Remediation

Patch, then assume compromise.

Apply vendor-provided patches, updates, or TCP stack fixes that address the Sockstress-related TCP state handling weakness and persist-condition resource exhaustion behavior. Because the vulnerability affects multiple vendors and products, remediation is implementation-specific and should follow the affected vendor’s security advisory and patch guidance for the relevant operating system, appliance, or network product.

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
BsdBsdoperating_system
BsdiBsd Osoperating_system
Cisco SystemsCatalyst Blade Switch 3020 Firmwareoperating_system
Cisco SystemsCatalyst Blade Switch 3120 Firmwareoperating_system
Cisco SystemsCatalyst Blade Switch 3120x Firmwareoperating_system
Cisco SystemsIosoperating_system
DragonFly BSDDragonflybsdoperating_system
FreebsdFreebsdoperating_system
LinuxLinux Kerneloperating_system
Microsoft CorporationWindows 2000operating_system
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Vistaoperating_system
Microsoft CorporationWindows Xpoperating_system
MidnightbsdMidnightbsdoperating_system
NetbsdNetbsdoperating_system
OpenbsdOpenbsdoperating_system
Oracle CorporationSolarisoperating_system
TrustedbsdTrustedbsdoperating_system
FAQ

Frequently asked questions

Is CVE-2008-4609 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-4609 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-4609?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2008-4609, the earliest disclosed May 6, 2016.
Is there a patch for CVE-2008-4609?
Apply vendor-provided patches, updates, or TCP stack fixes that address the Sockstress-related TCP state handling weakness and persist-condition resource exhaustion behavior. Because the vulnerability affects multiple vendors and products, remediation is implementation-specific and should follow the affected vendor’s security advisory and patch guidance for the relevant operating system, appliance, or network product.
What products are affected by CVE-2008-4609?
Bsd, Linux Kernel, Bsdi Bsd Os, Cisco Systems Catalyst Blade Switch 3020 Firmware, Cisco Systems Catalyst Blade Switch 3120 Firmware, and 14 more.
How severe is CVE-2008-4609?
CVE-2008-4609 has a CVSS v2 score of 7.1 (High) and an EPSS score of 32.4% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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.