Sockstress TCP Connection Queue Exhaustion DoS
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
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.
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.
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.
1 exploit validated by Mallory's analysis.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.