What is the CVSS score of CVE-2014-2959?

CVE-2014-2959 has a CVSS 2.0 base score of 9.0 (Critical). CVSS vector: AV:N/AC:L/Au:N/C:C/I:P/A:P. EPSS exploitation probability: 1.5%.

Powervault Ml6000 Firmware CVE-2014-2959

CRITICAL

OS Command Injection (CWE-78)

2014-06-02 cret@cert.org

Command Injection Dell Powervault Ml6000 Firmware Powervault Ml6000 Scalar I500 Firmware Scalar I500

9.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

9.0 CRITICAL

AV:N/AC:L/Au:N/C:C/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:C/I:P/A:P

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 02, 2014 - 19:55 cve.org

CRITICAL 9.0

DescriptionCVE.org

logViewer.htm on the Dell ML6000 tape backup system with firmware before i8.2.0.2 (641G.GS103) and the Quantum Scalar i500 tape backup system with firmware before i8.2.2.1 (646G.GS002) allows remote attackers to execute arbitrary commands via shell metacharacters in a pathname parameter.

AnalysisAI

logViewer.htm on the Dell ML6000 tape backup system with firmware before i8.2.0.2 (641G.GS103) and the Quantum Scalar i500 tape backup system with firmware before i8.2.2.1 (646G.GS002) allows remote. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. logViewer.htm on the Dell ML6000 tape backup system with firmware before i8.2.0.2 (641G.GS103) and the Quantum Scalar i500 tape backup system with firmware before i8.2.2.1 (646G.GS002) allows remote attackers to execute arbitrary commands via shell metacharacters in a pathname parameter. Affected products include: Dell Powervault Ml6000 Firmware, Dell Powervault Ml6000, Quantum Scalar I500 Firmware, Quantum Scalar I500.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.