What is the CVSS score of CVE-2018-10730?

CVE-2018-10730 has a CVSS 3.0 base score of 9.1 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 4.6%.

Is there a patch available for CVE-2018-10730?

Yes, a patch is available for CVE-2018-10730. Update the affected software to the latest version immediately.

Fl Switch 3005 Firmware CVE-2018-10730

CRITICAL

OS Command Injection (CWE-78)

2018-05-17 cve@mitre.org

9.1

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

9.1 CRITICAL

AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

May 17, 2018 - 19:29 nvd

CRITICAL 9.1

DescriptionNVD

All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection.

AnalysisAI

All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, low attack complexity.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection. Affected products include: Phoenixcontact Fl Switch 3005 Firmware, Phoenixcontact Fl Switch 3005T Firmware, Phoenixcontact Fl Switch 3004T-Fx Firmware, Phoenixcontact Fl Switch 3004T-Fx St Firmware, Phoenixcontact Fl Switch 3008 Firmware. Version information: version 1.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.