Loading vulnerability…
A vulnerability in Avahi before 0.6.24 exists in the originates_from_local_legacy_unicast_socket function (avahi-core/server.c) of avahi-daemon. Remote attackers can trigger an assertion failure and crash the daemon by sending a specially crafted mDNS packet with a source port of 0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/mdns/avahi_portzero.rb) that exploits a denial of service vulnerability (CVE-2008-5081) in avahi-daemon versions prior to 0.6.24. The exploit works by sending a specially crafted UDP packet with a source port of 0 to the target's mDNS port (5353/UDP). If the target is vulnerable, this causes the avahi-daemon to crash, resulting in a denial of service. The module is written in Ruby and leverages Metasploit's auxiliary and capture libraries. The only required input is the target's IP address (rhost), and the default destination port is 5353. The exploit is operational and does not provide a shell or code execution, but rather disrupts the target service.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.