CVE-2018-10728 json
All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows (a diffe…
published 2018-05-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-2798
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows (a different vulnerability than CVE-2018-10731).
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-137-02 updated cvss 8.1
PHOENIX CONTACT FL SWITCH 3xxx/4xxx/48xx Series
-
PHOENIX CONTACT, Innominate Security Technologies All FL SWITCH 3xxx 4xxx and 48xxx Series products running firmware >= 1.0, <= 1.32affected: mitigation “FL SWITCH 3005”
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.18% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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 |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
ics-cert.us-cert.gov
/advisories/ICSA-18-137-02
patch, third-party-advisory, us-government-resource
-
cert.vde.com
/de-de/advisories/vde-2018-006
patch, third-party-advisory
-
securityfocus.com
/bid/104231
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-10728
- NVD CVE-2018-10728
Fencer Vulns 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.