Loading vulnerability…
Multiple stack-based buffer overflows exist in RealNetworks RealPlayer before 17.0.4.61 on Windows and before 12.0.1.1738 on Mac. The vulnerabilities are triggered when parsing a long version number or encoding declaration in the XML declaration of an RMP file. This allows remote attackers to exploit the overflow and execute 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-based buffer overflow vulnerability (CVE-2013-7260) in RealNetworks RealPlayer versions 16.0.3.51 and 16.0.2.32 on Windows XP SP2/SP3. The exploit works by generating a malicious .RMP (RealPlayer Metadata Package) file with an overlong version attribute in the XML declaration. When a victim opens this file in a vulnerable RealPlayer installation, a crafted payload is executed, allowing arbitrary code execution. The module uses ROP (Return-Oriented Programming) chains with gadgets from msvcrt.dll and mswmdm.dll to bypass DEP (Data Execution Prevention). The payload is customizable and can be any Metasploit-compatible shell or command. The attack vector is local, requiring user interaction to open the malicious file. The repository is structured as a single Ruby file compatible with the Metasploit framework, and all exploit logic is contained within this 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.
1 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.