CVE-2005-0065: The original design of TCP does not check that the TCP sequence number in an ICMP error message is within t...

Security readout for executives and security teams

This is a TCP design weakness: forged ICMP error messages may disrupt existing TCP connections or reduce throughput. The bundle does not identify specific affected products, versions, active exploitation, or a definitive patch. Business impact is mainly availability risk for systems whose TCP stacks still accept unauthenticated ICMP errors too broadly. Exposure depends on the TCP/IP stack implementation in operating systems, routers, firewalls, and embedded devices. The provided CVE data lists no affected vendors, products, versions, or CPEs, so asset-specific exposure cannot be determined from this bundle alone. Set priority after confirming whether legacy or embedded network stacks remain in use. For modern supported platforms, urgency is likely lower, but unvalidated infrastructure should be reviewed because the impact is availability disruption across TCP-dependent services. Mitigation focus: Check vendor guidance for TCP/IP stack ICMP error validation behavior.; Prioritize supported operating systems, routers, firewalls, and embedded network stacks.; Apply vendor patches or hardening that validates ICMP errors against active TCP state..

Prepared

Jun 30, 2026, 01:38 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.