CVE-2012-1831 in the critical feed json
Heap-based buffer overflow in WellinTech KingView 6.53 allows remote attackers to execute arbitrary code via a crafted packet to TCP port 5…
published 2012-07-05 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1841
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.8%
- EPSS 15.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Heap-based buffer overflow in WellinTech KingView 6.53 allows remote attackers to execute arbitrary code via a crafted packet to TCP port 555.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-12-185-01 updated cvss 10.0
WellinTech KingView Multiple Vulnerabilities
-
WellinTech KingHistorian 3.0. WellinTech KingView 6.53affected: mitigation “WellinTech has developed patches to resolve these issues. The WellinTech advisory and the KingView product patch can be found here: (http://www.wellintech.com/index.php/news/33-patch-for-kingview653).”
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
- First public exploit (EDB-19389)
- Published
Exploit prediction
15.77% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-19389 Kingview Touchview 6.53 - Multiple Heap Overflow Vulnerabilities dos, 2012-06-25
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
-
us-cert.gov
/control_systems/pdf/ICSA-12-185-01.pdf
patch, us-government-resource
-
wellintech.com
/index.php/news/33-patch-for-kingview653
patch, vendor-advisory
Sources
- CVE List CVE-2012-1831
- NVD CVE-2012-1831
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.