CVE-2017-13999 json
A Stack-based Buffer Overflow issue was discovered in WECON LEVI Studio HMI Editor v1.8.1 and prior.
published 9y ago modified 4mo ago also EUVD-2017-5514
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
A Stack-based Buffer Overflow issue was discovered in WECON LEVI Studio HMI Editor v1.8.1 and prior. Multiple stack-based buffer overflow vulnerabilities have been identified in which the application does not verify string size before copying to memory; the attacker may then be able to crash the application or run arbitrary code.
Is CVE-2017-13999 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-17-285-02 updated cvss 7.5
WECON Technology Co., Ltd. LeviStudio HMI Editor
-
WECON LEVI Studio HMI Editor <= 1.8.1affected: mitigation “WECON recommends that users update to v1.8.2”
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.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- n/a WECON Technology Co., Ltd. LeviStudio HMI Editor
Classification
References
-
ics-cert.us-cert.gov
/advisories/ICSA-17-285-02
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/101250
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102493
vdb-entry
Sources
- CVE List CVE-2017-13999
- NVD CVE-2017-13999
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.