Buffer overflow in the Private Communications Transport (PCT) protocol implementation in the Microsoft SSL library (PCT 1.0 handshake processing). A remote attacker can trigger the overflow by sending crafted PCT 1.0 handshake packets to a service/application using the affected Microsoft SSL library, resulting in arbitrary code execution.
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 module (ms04_011_pct.rb) that exploits a buffer overflow vulnerability in the Microsoft Windows SSL PCT protocol stack (CVE-2003-0719, MS04-011). The exploit targets Windows 2000 (SP0-SP4) and Windows XP (SP0, SP1) systems running SSL-enabled services, such as SMTP with STARTTLS or raw SSL services. The module connects to the specified TCP port, optionally negotiates SMTP STARTTLS, and sends a specially crafted buffer to trigger the overflow and execute arbitrary code (payload) on the target. The payload is provided by the Metasploit framework and can be customized by the user. The exploit requires the attacker to select the correct target version for reliable exploitation. The code is written in Ruby and is structured as a standard Metasploit exploit module, making use of the framework's payload and handler systems.
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.