Loading vulnerability…
A buffer overflow vulnerability exists in the prescan function of Sendmail 8.12.9. The flaw can be exploited by remote attackers to execute arbitrary code. The vulnerability is triggered via the parseaddr function in parseaddr.c, which fails to properly validate input, leading to a buffer overflow condition.
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 located at modules/auxiliary/dos/smtp/sendmail_prescan.rb. The module is a proof-of-concept denial of service (DoS) exploit targeting Sendmail versions 8.12.8 and earlier. It exploits a memory corruption vulnerability in the prescan() function when parsing SMTP headers, specifically by sending a maliciously crafted RCPT TO command to the SMTP service. The exploit is network-based and requires access to the target's SMTP port (typically TCP port 25). The payload is designed to crash the Sendmail process, as evidenced by the included gdb output showing a segmentation fault. The module does not provide code execution, only service disruption. The code is written in Ruby and leverages Metasploit's auxiliary and SMTP modules. No hardcoded IPs, domains, or file paths are present; the only fingerprintable endpoint is the SMTP service itself.
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.