Skip to content
Fencer Intel
critical 10.0

CVE-2012-4711 in the critical feed json

Buffer overflow in kingMess.exe 65.20.2003.10300 in WellinTech KingView 6.52, kingMess.exe 65.20.2003.10400 in KingView 6.53, and kingMess.…

published 2013-02-15 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4636

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
60.6%
EPSS 60.6% chance of exploitation in 30 days, percentile 99.1%
public exploits
2
Metasploit, Exploit-DB

Summary

Buffer overflow in kingMess.exe 65.20.2003.10300 in WellinTech KingView 6.52, kingMess.exe 65.20.2003.10400 in KingView 6.53, and kingMess.exe 65.50.2011.18049 in KingView 6.55 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted packet.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-043-02A updated cvss 10.0

WellinTech KingView KingMess Buffer Overflow

  • WellinTech KingView 6.52_kingMess.exe_65.20.2003.10300, 6.53_kingMess.exe_65.20.2003.10400, 6.55_kingMess.exe_65.50.2011.18049
    affected: mitigation “WellinTech recommends that all customers using KingView 6.52, 6.53, or 6.55 download the patch for their version of KingView that mitigates this vulnerability.”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (Metasploit exploit/windows/fileformat/kingview_kingmess_kvl)
  2. Published

Exploit prediction

60.62% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.