First published: Thu May 17 2018(Updated: )
All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Phoenixcontact Fl Switch 3005 Firmware | >1.0<=1.33 | |
Phoenixcontact Fl Switch 3005 | ||
Phoenixcontact Fl Switch 3005t Firmware | >=1.0<=1.33 | |
Phoenix Contact FL Switch 3005T | ||
Phoenixcontact Fl Switch 3004t-fx St Firmware | >=1.0<=1.33 | |
Phoenix Contact FL Switch 3004T-FX | ||
Phoenixcontact Fl Switch 3004t-fx St Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3004t-fx St Firmware | ||
Phoenixcontact Fl Switch 3008 Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3008 | ||
Phoenixcontact Fl Switch 3008t Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3008t Firmware | ||
Phoenixcontact Fl Switch 3006t-2fx Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3006t-2fx Sm Firmware | ||
Phoenix Contact FL Switch 3006T-2FX ST Firmware | >=1.0<=1.33 | |
Phoenix Contact FL Switch 3006T-2FX ST Firmware | ||
Phoenixcontact FL Switch 3012e-2sfx | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3012e-2sfx Firmware | ||
Phoenixcontact Fl Switch 3016e Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3016e Firmware | ||
Phoenixcontact FL Switch 3016t Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3016 | ||
Phoenixcontact FL Switch 3016t Firmware | >=1.0<=1.33 | |
Phoenixcontact FL Switch 3016t Firmware | ||
Phoenixcontact Fl Switch 3006t-2fx Sm Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3006t-2fx Sm Firmware | ||
Phoenixcontact Fl Switch 4008t-2sfp Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4008t-2sfp Firmware | ||
Phoenixcontact Fl Switch 4008t-2gt-4fx Sm | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4008t-2gt-4fx Sm Firmware | ||
Phoenixcontact Fl Switch 4008t-2gt-3fx Sm | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4008t-2gt-3fx Sm Firmware | ||
Phoenixcontact Fl Switch 4808e-16fx Lc-4gc | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx Lc-4gc Firmware | ||
Phoenixcontact Fl Switch 4808e-16fx Sm-4gc Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx Sm-4gc Firmware | ||
Phoenixcontact Fl Switch 4808e-16fx Sm St-4gc | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx Sm St-4gc Firmware | ||
Phoenix Contact FL Switch 4808E-16FX ST-4GC | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx St-4gc Firmware | ||
Phoenixcontact Fl Switch 4808e-16fx Sm Lc-4gc Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx-4gc | ||
Phoenixcontact Fl Switch 4808e-16fx Sm Lc-4gc Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4808e-16fx Sm Lc-4gc Firmware | ||
Phoenixcontact FL Switch 4012T 2GT 2FX | >=1.0<=1.33 | |
Phoenix Contact FL Switch 4012T-2GT-2FX ST Firmware | ||
Phoenixcontact FL Switch 4012T 2GT 2FX | >=1.0<=1.33 | |
Phoenixcontact FL Switch 4012T 2GT 2FX | ||
Phoenixcontact Fl Switch 4824e-4gc Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4824e-4gc | ||
Phoenixcontact Fl Switch 4800e-24fx Sm-4gc Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4800e-24fx Sm-4gc Firmware | ||
Phoenixcontact Fl Switch 4800e-24fx Sm-4gc | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4800e-24fx Sm-4gc Firmware | ||
Phoenixcontact Fl Switch 3012e-2fx Sm Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 3012e-2fx Sm Firmware | ||
Phoenixcontact Fl Switch 4000t-8poe-2sfp-r Firmware | >=1.0<=1.33 | |
Phoenixcontact Fl Switch 4000t-8poe-2sfp-r Firmware |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-10730 is classified as a critical vulnerability due to the potential for OS command injection.
To fix CVE-2018-10730, update the firmware of the affected Phoenix Contact FL SWITCH to a version later than 1.33.
CVE-2018-10730 affects all Phoenix Contact managed FL SWITCH 3xxx, 4xxx, and 48xx products running firmware versions from 1.0 to 1.33.
CVE-2018-10730 is an OS command injection vulnerability, allowing attackers to execute arbitrary commands on the system.
CVE-2018-10730 was publicly disclosed in May 2018.