Loading vulnerability…
A buffer overflow vulnerability exists in kingMess.exe in WellinTech KingView versions 6.52, 6.53, and 6.55. Specifically, the affected versions are kingMess.exe 65.20.2003.10300 (KingView 6.52), 65.20.2003.10400 (KingView 6.53), and 65.50.2011.18049 (KingView 6.55). The vulnerability can be triggered by sending a specially crafted packet to the service, resulting in memory corruption.
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 buffer overflow vulnerability (CVE-2012-4711) in KingView <= 6.55, specifically in the KingMess.exe application when parsing .kvl log files. The exploit works by generating a specially crafted .kvl file that, when opened by a victim using the 'Browse Log Files' feature in KingMess.exe, triggers a buffer overflow due to insecure usage of sprintf. The module allows the attacker to specify a payload (up to 1408 bytes, with certain bad characters filtered) that will be executed with the privileges of the user running KingMess.exe. The exploit has been tested on KingView 6.52 and 6.53 Free Trial on Windows XP SP3. The attack vector is local, requiring user interaction to open the malicious file. The repository is structured as a standard Metasploit module written in Ruby, and the main entry point is the provided .rb 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.
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.