Loading vulnerability…
A buffer overflow vulnerability exists in VideoSpirit Pro 1.6.8.1 and possibly earlier versions, as well as VideoSpirit Lite 1.4.0.1 and possibly other versions. The vulnerability is triggered when a specially crafted VideoSpirit project (.visprj) file containing a valitem element with an excessively long "name" attribute is processed. This can result in a buffer overflow condition, potentially allowing 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 (modules/exploits/windows/fileformat/videospirit_visprj.rb) targeting a stack buffer overflow vulnerability in VeryTools Video Spirit Pro version 1.70 and earlier (CVE-2011-0499, CVE-2011-0500). The exploit works by generating a specially crafted .visprj project file, which, when opened by the vulnerable application on Windows XP, Vista, or 7, triggers a buffer overflow. The module uses a ROP chain to bypass DEP and ASLR protections, allowing arbitrary code execution. The payload is customizable via Metasploit and can be up to 800 bytes. The exploit does not require network interaction; the attack vector is local, relying on social engineering to convince a user to open the malicious file. The repository is structured as a standard 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.