A stack-based buffer overflow vulnerability exists in dnsmasq before version 2.78. The flaw is triggered when dnsmasq processes a specially crafted DHCPv6 request, leading to a buffer overflow on the stack. This can be exploited remotely by an attacker to crash the service or potentially execute arbitrary code with the privileges of the dnsmasq process.
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 Python proof-of-concept exploit for CVE-2017-14493, a buffer overflow vulnerability in dnsmasq's DHCPv6 code. The main file, 'bof-dnsmasq-cve-2017-14493.py', constructs a specially crafted DHCPv6 packet containing a ROP chain and shell command payload. The exploit targets a remote dnsmasq service over IPv6 UDP (port 547), aiming to trigger the buffer overflow and execute arbitrary code. The payload attempts to launch a netcat listener on the target, providing a shell to the attacker. The repository is structured simply, with a README and the exploit script. The exploit is operational, requiring the attacker to specify the target's IPv6 address and port. No hardcoded IPs or domains are present; the script takes these as arguments. The exploit is not part of a framework and is a standalone POC with a working payload.
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.