A stack-based buffer overflow exists in the MOVIEPLAYER.MoviePlayerCtrl.1 ActiveX control (MoviePlayer.ocx version 6.8.0.0) as distributed with Viscom Software Movie Player Pro SDK ActiveX 6.8. The vulnerability is triggered by passing an overly long string to the strFontName parameter of the DrawText method, resulting in a stack buffer overflow and potential 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 (Ruby file) that exploits a stack-based buffer overflow vulnerability in the Viscom Software Movie Player Pro SDK ActiveX control (MoviePlayer.ocx version 6.8.0.0). The exploit targets the DrawText method, specifically the strFontName parameter, allowing remote code execution when a victim visits a malicious web page using Internet Explorer (IE6, IE7, or IE8 with Java support) on Windows XP, Vista, or Windows 7. The module uses a combination of JavaScript heap spraying and VBScript to trigger the overflow and deliver a customizable Metasploit payload. The exploit includes ROP chains to bypass DEP and ASLR on supported platforms. The only file in the repository is the Metasploit module itself, written in Ruby, and it is fully operational for use within the Metasploit Framework. The main fingerprintable endpoints are the vulnerable ActiveX control file (MoviePlayer.ocx) and its CLSID. The exploit is not a detection script or a fake; it is a real, operational browser-based exploit module.
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.