Loading vulnerability…
A stack-based buffer overflow exists in the news reader component (MSOE.DLL) of Microsoft Outlook Express versions 5.5 SP2, 6, and 6 SP1. The vulnerability is triggered when a remote NNTP server sends a LIST response containing an excessively long second field, which is not properly bounds-checked by the client, leading to a buffer overflow on the stack.
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 single Metasploit exploit module targeting a stack buffer overflow vulnerability (CVE-2005-1213) in Microsoft Outlook Express's NNTP response parsing. The exploit works by running a malicious NNTP server (default port 119) that sends a specially crafted response to a connecting Outlook Express client, triggering the buffer overflow and allowing arbitrary code execution. The module supports two main targets: Windows 2000 English SP0-SP4 and Windows XP English SP0/SP1. The payload is customizable via Metasploit and is delivered when the vulnerable client connects. The code is written in Ruby and follows the standard Metasploit module structure, including payload handling, SEH exploitation, and network server setup. No hardcoded IP addresses or domains are present, but the exploit is fingerprintable by its use of TCP port 119 as an NNTP server.
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.