Loading vulnerability…
A buffer overflow vulnerability exists in MailCarrier 2.51, where remote attackers can trigger a buffer overflow by sending an excessively long string to certain commands, including SMTP RCPT TO and various POP3 commands (USER, LIST, TOP, RETR). This flaw allows for the execution of arbitrary code on the affected system.
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 proof-of-concept (PoC) exploit for CVE-2019-11395, a buffer overflow vulnerability in MailCarrier 2.51's POP3 service. The main exploit file, 'CVE–2019–11395.py', is a Python script that constructs a specially crafted buffer to overflow the stack and overwrite the EIP register, allowing the execution of arbitrary shellcode. The script is designed to connect to a target POP3 service (default port 110) and send the malicious payload via the 'USER' command. The shellcode and target IP must be supplied by the user. The README.md provides detailed instructions on how to discover the vulnerability, find the offset, identify a suitable JMP ESP address, generate shellcode, and execute the exploit. The exploit is intended for academic and testing purposes, demonstrating the process of exploiting a buffer overflow vulnerability in a network service.
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.