Loading vulnerability…
CVE-2006-0027 is an unspecified vulnerability in Microsoft Exchange in which remote attackers can execute arbitrary code by sending e-mail messages containing crafted vCal or iCal calendar properties. Based on the available information, the flaw is triggered during Exchange processing of calendar data embedded in e-mail messages, but the specific vulnerable function or parsing routine is not provided in the source content.
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 single Metasploit auxiliary module targeting a denial of service (DoS) vulnerability in Microsoft Exchange (MS06-019, CVE-2006-0027). The exploit works by sending a specially crafted SMTP email message with malformed VCAL MODPROP values, which triggers a heap overflow and crashes the Exchange service. The module is written in Ruby and leverages Metasploit's SMTP and DoS mixins. The only file present is the exploit module itself, which is operational as a proof-of-concept (POC) for causing a service crash. The exploit requires network access to the target's SMTP service (typically port 25). No post-exploitation or shell payload is provided; the sole effect is denial of service. The code is structured as a standard Metasploit module, with configuration options for the email subject and required SMTP parameters.
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.
2 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.