Loading vulnerability…
A buffer overflow exists in Microsoft Visual Basic 6.0 and Enterprise Edition 6.0 SP6, triggered when a user opens a Visual Basic project (vbp) file containing an excessively long Reference line. The vulnerability is related to the VBP_Open and OLE components. Exploitation requires user interaction to open a maliciously crafted VBP file, which can result in arbitrary code execution.
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 (ms_visual_basic_vbp.rb) that exploits a stack buffer overflow vulnerability (CVE-2007-4776) in Microsoft Visual Basic 6.0. The exploit works by generating a specially crafted Visual Basic Project (.vbp) file with an overly long 'Reference' line, which triggers a buffer overflow when opened in the vulnerable application. The module allows the attacker to embed any compatible Metasploit payload (default is a reverse TCP shell) into the malicious file. The exploit targets Windows XP (SP0-SP3 x86 and SP1-SP2 x86-64, English). The attack vector is local, requiring the victim to open the malicious file. The repository is structured as a standard Metasploit exploit module, written in Ruby, and leverages the Metasploit framework's file format exploitation capabilities. Notable fingerprintable endpoints include the generated .vbp file and a reference to the stdole2.tlb file in the Windows system 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.