CVE-2011-1002: avahi-core/socket.c in avahi-daemon in Avahi before 0.6.29 allows remote attackers to cause a denial of ser...

Security readout for executives and security teams

This flaw can let a remote sender crash or hang Avahi service behavior by sending an empty mDNS UDP packet to port 5353. The impact is denial of service, not data theft or code execution based on the provided sources. Business urgency is highest where Avahi supports discovery for operational Linux systems or embedded devices. Exposure is likely on systems running avahi-daemon with mDNS UDP port 5353 reachable. This commonly matters on local networks, appliances, desktops, and Linux hosts using service discovery. The bundle does not identify specific downstream product versions beyond Avahi before 0.6.29. Prioritize remediation in networks where Avahi supports service discovery for business-critical Linux, desktop, or embedded systems. This is not evidenced as ransomware-grade or code-execution risk, but a reachable daemon could disrupt discovery-dependent operations. Mitigation focus: Upgrade Avahi to 0.6.29 or vendor-fixed packages where applicable.; Review Red Hat, Debian, SUSE, or distributor advisories for package-specific fixes.; Disable avahi-daemon where mDNS service discovery is not required..

Prepared

Jun 24, 2026, 13:28 UTC (UTC+00:00)

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