Loading vulnerability…
A denial-of-service vulnerability exists in ntpd (Network Time Protocol daemon) prior to versions 4.2.4p8 and 4.2.6, where the handling of MODE_PRIVATE (mode 7) packets allows a remote attacker to trigger a continuous exchange of error responses between two ntpd instances. By sending a single spoofed UDP packet to port 123, an attacker can cause two ntpd daemons to enter an endless loop of error responses, consuming CPU and network bandwidth. The flaw is due to ntpd responding to error responses, creating a feedback loop.
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.
This repository contains a single Metasploit auxiliary module that exploits a denial of service vulnerability (CVE-2009-3563) in NTP.org's ntpd daemon. The exploit works by sending a specially crafted UDP packet (mode 7) to a vulnerable ntpd server, spoofed as coming from another vulnerable ntpd server. This causes both servers to enter an infinite response loop, resulting in a denial of service. The module requires the attacker to specify the spoofed source address (LHOST) and targets UDP port 123, which is standard for NTP. The code is written in Ruby and leverages Metasploit's auxiliary and capture modules. The exploit is operational and can be used to demonstrate or cause a DoS condition on affected NTP servers.
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.
1 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.
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.