Loading vulnerability…
CVE-2025-34123 is a stack-based buffer overflow in VideoCharge Studio 2.12.3.685 triggered while processing a specially crafted .VSC configuration file. According to the provided content, the vulnerable condition arises from improper handling of user-controlled data in the XML 'Name' attribute within the .VSC file. Supplying an overly long or malformed value can corrupt stack memory and cause an SEH overwrite condition during parsing. Successful exploitation can allow arbitrary code execution in the security context of the user who opens the malicious file.
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-based buffer overflow vulnerability in VideoCharge Studio version 2.12.3.685 (CVE-2025-34123). The exploit is implemented as a Ruby fileformat module, which generates a malicious .VSC (XML-based) configuration file. When this file is opened by a user in the vulnerable version of VideoCharge Studio on Windows, it triggers a SEH-based buffer overflow, allowing arbitrary code execution with the privileges of the user. The module allows the attacker to specify a custom payload (up to 2808 bytes, with certain bad characters filtered) and outputs the malicious file (default name: msf.vsc). The exploit does not require network interaction; exploitation is achieved by convincing a user to open the crafted 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.
3 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.