Loading vulnerability…
A buffer overflow vulnerability exists in VideoCharge Software Watermark Master version 2.2.23. The vulnerability is triggered when a specially crafted .wcf file containing an overly long string in the SourcePath value is processed. This allows remote attackers to overflow a buffer and potentially execute arbitrary code within the context of the application.
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/watermark_master.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2013-6935) in Watermark Master 2.2.23 for Windows. The exploit works by generating a specially crafted .WCF configuration file containing a malicious payload. When a victim opens this file with Watermark Master, the buffer overflow is triggered, allowing arbitrary code execution with the privileges of the user. The module supports both 32-bit and 64-bit versions of Windows 7 running Watermark Master 2.2.23. The exploit is operational and allows the attacker to specify a payload, which is encoded and embedded in the malicious file. The attack vector is local, requiring user interaction to open the file. The only fingerprintable endpoint is the .WCF file format itself, which is the vehicle for exploitation. The code is written in Ruby and is structured as a standard Metasploit file format 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.