CVE-2016-4509 json
Heap-based buffer overflow in elcsoft.exe in Eaton ELCSoft 2.4.01 and earlier allows remote authenticated users to execute arbitrary code v…
published 2016-07-03 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5496
- cvss
- 6.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Heap-based buffer overflow in elcsoft.exe in Eaton ELCSoft 2.4.01 and earlier allows remote authenticated users to execute arbitrary code via a crafted file.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-182-01 updated cvss 6.0
Eaton ELCSoft Programming Software Memory Vulnerabilities
-
Eaton ELCSoft <=2.4.01affected: mitigation “Eaton has released a revision that mitigates these vulnerabilities. The revision can be downloaded at (https://eatonfilesharing.box.com/s/r4ulykfay2x5nlai9pqijivdh1zyks98)” eatonfilesharing.box.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
1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.0 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
ics-cert.us-cert.gov
/advisories/ICSA-16-182-01
third-party-advisory, us-government-resource
- zerodayinitiative.com /advisories/ZDI-16-408
-
securityfocus.com
/bid/91524
vdb-entry
Sources
- CVE List CVE-2016-4509
- NVD CVE-2016-4509
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.