Loading vulnerability…
CVE-2011-5171 describes multiple stack-based buffer overflow vulnerabilities in CyberLink Power2Go versions 7 (build 196) and 8 (build 1031). The vulnerabilities are triggered when the application parses a specially crafted p2g project file containing overly long values in the 'src' or 'name' parameters. This can result in the overwriting of stack memory, potentially allowing for the execution of arbitrary code.
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 targeting a stack buffer overflow vulnerability (CVE-2011-5171) in CyberLink Power2Go version 8.x for Windows. The exploit works by generating a specially crafted .p2g project file with an overly long 'name' attribute, which, when opened by a vulnerable version of Power2Go, triggers a buffer overflow and allows execution of arbitrary code. The module allows the attacker to specify a payload (such as a reverse shell) that will be executed with the privileges of the user who opens the file. The exploit is operational and leverages Metasploit's payload and encoder infrastructure. The only fingerprintable endpoint is the malicious .p2g file itself. The repository structure is typical for a Metasploit exploit module, with all logic contained in a single Ruby file under the appropriate directory.
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.