CVE-2019-6539 json
Several heap-based buffer overflow vulnerabilities in WECON LeviStudioU version 1.8.56 and prior have been identified, which may allow arbi…
published 2019-02-13 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16098
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Several heap-based buffer overflow vulnerabilities in WECON LeviStudioU version 1.8.56 and prior have been identified, which may allow arbitrary code execution. Mat Powell, Ziad Badawi, and Natnael Samson working with Trend Micro's Zero Day Initiative, reported these vulnerabilities to NCCIC.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-036-03 updated cvss 7.8
WECON LeviStudioU (Update A)
-
WECON LeviStudioU <= 1.8.69affected: mitigation “For more information contact WECON customer service: Phone: 0086-591-87868869-894 Website: http://www.we-con.com.cn/en/message.html”
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
Exploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- ICS-CERT WECON LeviStudioU
Classification
References
-
ics-cert.us-cert.gov
/advisories/ICSA-19-036-03
patch, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/106861
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-6539
- NVD CVE-2019-6539
Fencer Vulns 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.