Loading vulnerability…
A stack-based buffer overflow exists in NewsGator FeedDemon 2.7 and earlier, triggered by processing a .opml file containing an outline element with an excessively long text attribute. The vulnerable code fails to properly validate the length of the text attribute before copying it to a stack buffer, leading to potential 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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/feeddemon_opml.rb) that exploits a stack buffer overflow vulnerability in FeedDemon (CVE-2009-0546). The exploit works by generating a specially crafted OPML file (default name: msf.opml) that, when imported into FeedDemon, triggers a buffer overflow and allows arbitrary code execution. The module is written in Ruby and leverages Metasploit's payload generation and encoding capabilities to avoid bad characters. The exploit targets Windows platforms and is operational, allowing the attacker to execute any Metasploit-compatible payload. The only fingerprintable endpoints are the malicious OPML file and the FeedDemon.exe binary. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single file.
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.