Loading vulnerability…
Exim through version 4.97.1 incorrectly parses multiline RFC 2231 filename headers. A remote attacker can craft a message attachment header that bypasses a $mime_filename-based extension-blocking protection rule, potentially allowing executable attachments to be delivered to end-user mailboxes.
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 provides a Python proof-of-concept (PoC) exploit for CVE-2024-39929, a vulnerability in Exim mail server versions up to 4.97.1. The exploit script (CVE-2024-39929_POC.py) reads a list of SMTP servers from a file (servers.txt) and sends a specially crafted email to each server. The email contains an attachment with a filename split across multiple Content-Disposition headers (filename*0, filename*1, filename*2), which is designed to bypass Exim's file extension blocking and allow delivery of executable files (e.g., .exe) to user mailboxes. The script prompts the user for sender and recipient email addresses and connects to each SMTP server on port 25. The README.md provides detailed usage instructions, ethical considerations, and references. The exploit is a network-based attack targeting Exim SMTP servers and requires a list of target servers to function. The code is a functional PoC and does not include weaponized or automated payload customization.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.