CVE-2005-1280: The rsvp_print function in tcpdump 3.9.1 and earlier allows remote attackers to cause a denial of service (...

Security readout for executives and security teams

A specially crafted RSVP network packet can make vulnerable tcpdump versions hang in an infinite loop while parsing traffic. The business impact is loss of packet-capture visibility, not confirmed system compromise. This mainly matters where tcpdump runs on exposed monitoring links, gateways, forensic hosts, or automated capture pipelines. Exposure is most likely on legacy Unix/Linux systems still running tcpdump 3.9.1 or earlier, especially packet monitoring systems that inspect untrusted network traffic. The affected-product metadata is incomplete, so inventory validation is necessary. Prioritize as a legacy exposure cleanup item unless tcpdump is central to security monitoring. It can blind capture workflows or disrupt forensic collection, but the provided sources support denial of service only, not code execution or confirmed active exploitation. Mitigation focus: Inventory tcpdump versions across monitoring, server, and appliance environments.; Upgrade tcpdump through supported vendor security packages or vendor guidance.; Apply relevant Red Hat, Fedora, SCO, or platform advisories where applicable..

Prepared

Jun 29, 2026, 22:16 UTC (UTC+00:00)

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