CVE-2019-6541 json
A memory corruption vulnerability has been identified in WECON LeviStudioU version 1.8.56 and prior, which may allow arbitrary code executi…
published 7y ago modified 4mo ago also EUVD-2019-16100
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
A memory corruption vulnerability has been identified in WECON LeviStudioU version 1.8.56 and prior, 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
Is CVE-2019-6541 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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
1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- ICS-CERT WECON LeviStudioU
Classification
References
-
ics-cert.us-cert.gov
/advisories/ICSA-19-036-03
mitigation, patch, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/106861
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-6541
- NVD CVE-2019-6541
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.