CVE-2018-7511 json
In Eaton ELCSoft versions 2.04.02 and prior, there are multiple cases where specially crafted files could cause a buffer overflow which, in…
published 8y ago modified 4mo ago also EUVD-2018-19240
- cvss
- 5.3
- 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 81%
- public exploits
- 0
- none known
Summary
In Eaton ELCSoft versions 2.04.02 and prior, there are multiple cases where specially crafted files could cause a buffer overflow which, in turn, may allow remote execution of arbitrary code.
Patch / fix
- eaton elcsoft 2.04.02
Is CVE-2018-7511 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-18-065-03 updated cvss 6.3
Eaton ELCSoft
-
Eaton ELCSoft <=2.04.02affected: vendor fix, mitigation “Eaton states the current firmware needs to be uninstalled prior to loading the update.”
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.02% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Eaton Eaton ELCSoft
Classification
References
-
eaton.com
/ecm/idcplg?IdcService=GET_FILE&allowInterrupt=1&RevisionSelectionMethod=LatestReleased&noSaveAs=0&Rendition=P
vendor-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-065-03
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/103301
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-7511
- NVD CVE-2018-7511
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.