CVE-2020-16219 json
Delta Electronics TPEditor Versions 1.97 and prior.
published 6y ago modified 4mo ago also EUVD-2020-8185
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Delta Electronics TPEditor Versions 1.97 and prior. An out-of-bounds read may be exploited by processing specially crafted project files. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute arbitrary code, and/or crash the application.
Is CVE-2020-16219 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-20-219-04 updated cvss 7.8
Delta Industrial Automation TPEditor
-
Delta Electronics TPEditor <= 1.97affected: vendor fix deltaww.com
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.64% chance of exploitation in the next 30 days, higher than 85% 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
- n/a Delta Electronics TPEditor
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
us-cert.cisa.gov
/ics/advisories/icsa-20-219-04
third-party-advisory, us-government-resource
-
zerodayinitiative.com
/advisories/ZDI-20-961/
third-party-advisory, vdb-entry
-
zerodayinitiative.com
/advisories/ZDI-20-963/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2020-16219
- NVD CVE-2020-16219
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.