Multiple stack-based buffer overflows exist in several ActiveX controls used by Logitech VideoCall, specifically in VibeC (vibecontrol.dll), CallManager and ViewerClient (StarClient.dll), ComLink (uicomlink.dll), and WebCamXMP (wcamxmp.dll). These vulnerabilities allow remote attackers to trigger a denial of service (browser crash) or execute arbitrary code via unspecified vectors, likely through crafted input to the affected ActiveX controls.
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.
This repository contains a single Metasploit module targeting a stack buffer overflow vulnerability in the Logitech VideoCall ActiveX Control (wcamxmp.dll version 2.0.3470.448), identified as CVE-2007-2918. The exploit is delivered via a malicious HTTP server that serves a crafted HTML page with embedded JavaScript. When a vulnerable client visits the page, the script instantiates the vulnerable ActiveX control using its CLSID and calls the Start() method with an overly long string, triggering the buffer overflow and executing attacker-supplied code. The module allows for customizable payloads (default 800 bytes) and is designed for Windows XP Pro SP2 English. The main file is written in Ruby and leverages Metasploit's HttpServer::HTML mixin to serve the exploit. The repository is operational and provides a working exploit for remote code execution via browser-based attack vectors.
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.