Loading vulnerability…
A stack-based buffer overflow vulnerability exists in MicroP version 0.1.1.1600. The vulnerability can be triggered by a remote attacker supplying a specially crafted .mppl file, which causes a buffer overflow condition. While initial reports suggested the overflow occurs in the lpFileName parameter of the CreateFileA function, further analysis indicates the overflow is likely due to a separate, unnamed function within the application responsible for handling .mppl files.
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 (2 hidden).
This repository contains a single Metasploit module targeting a stack-based buffer overflow vulnerability in MicroP version 0.1.1.1600 (CVE-2010-5299). The exploit is implemented in Ruby and leverages the Metasploit framework's FILEFORMAT exploit mixin. The module generates a malicious .mppl file (default name: msf.mppl) that, when opened by a user in the vulnerable MicroP application on Windows XP SP3, Vista, or 7, triggers a buffer overflow and allows for arbitrary code execution. The payload is customizable (up to 728 bytes, avoiding certain bad characters) and is executed in the context of the user. The exploit does not require elevated privileges and is effective as a local attack vector, requiring user interaction to open the crafted file. The repository is structured as a typical Metasploit module, with all exploit logic contained in a single Ruby 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.