CVE-2018-10729 json
All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 allow reading the configuration file b…
published 8y ago modified 4mo ago also EUVD-2018-2799
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 allow reading the configuration file by an unauthenticated user.
Patch / fix
Is CVE-2018-10729 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-137-02 updated cvss 5.3
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
1.83% chance of exploitation in the next 30 days, higher than 78% 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:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
cert.vde.com
/de-de/advisories/vde-2018-005
patch, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-137-02
patch, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/104231
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-10729
- NVD CVE-2018-10729
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.