Loading vulnerability…
A buffer overflow vulnerability exists in the YVerInfo.GetInfo.1 ActiveX control (YVerInfo.dll) used by Yahoo! Messenger before version 8.1.0.419. The vulnerability is present in the fvCom() and info() methods, which improperly handle input arguments, allowing remote attackers to execute arbitrary code. Exploitation requires the attacker to induce the victim to visit a malicious web page, and to bypass domain restrictions by leveraging a cross-site scripting vulnerability on yahoo.com or by controlling the victim's DNS resolution for yahoo.com.
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 in the Yahoo! Messenger YVerInfo.dll ActiveX control (CVE-2007-4515). The exploit is delivered via a malicious HTML page served by the attacker's HTTP server. When a victim visits the page using Internet Explorer with the vulnerable ActiveX control installed, a specially crafted string is sent to the 'fvCom()' method, triggering a buffer overflow and allowing arbitrary code execution. The module allows for customizable payloads (default 800 bytes) and is operational, requiring the victim to be running Windows XP SP2 with the vulnerable Yahoo! Messenger component. The main fingerprintable endpoint is the ActiveX CLSID 'D5184A39-CBDF-4A4F-AC1A-7A45A852C883' and the vulnerable DLL 'YVerInfo.dll'. The code is written in Ruby and is structured as a standard Metasploit 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.