Loading vulnerability…
A use-after-free vulnerability exists in Exim versions prior to 4.94.2, specifically in the smtp_reset function. This issue can be triggered in certain scenarios, particularly in builds that use OpenSSL. The vulnerability arises when memory is freed but later accessed, potentially leading to undefined behavior.
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 is a proof-of-concept (POC) for CVE-2020-28018, a critical remote code execution vulnerability in Exim4 (version 4.93, as tested). The vulnerability is a use-after-free in the tls_write() function in tls-openssl.c, triggered via specially crafted pipelined SMTP commands when Exim is compiled with OpenSSL support. The repository contains the full Exim4-4.93 source tree, various patch files, build scripts, and documentation. The README provides a detailed technical explanation of the vulnerability, affected configurations, and exploitation prerequisites. The Makefile and build scripts facilitate compiling Exim with OpenSSL, which is required for the exploit. While the repository is primarily a POC and does not include a weaponized exploit script, it provides all necessary information and code to reproduce the vulnerability in a test environment. The main attack vector is network-based, targeting the SMTP service (typically on port 25/TCP) exposed by Exim4. No hardcoded IPs, domains, or external network endpoints are present; the exploit targets the local Exim4 service as configured. The repository is structured as a full source and patch set for Exim4, with supporting scripts and documentation for building and testing the vulnerable configuration.
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, 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.