What is the CVSS score of CVE-2015-7817?

CVE-2015-7817 has a CVSS 2.0 base score of 7.1 (High). CVSS vector: AV:N/AC:M/Au:N/C:C/I:N/A:N. EPSS exploitation probability: 0.2%.

System Networking Switch Center CVE-2015-7817

HIGH

Race Condition (CWE-362)

2015-11-12 cve@mitre.org

IBM Race Condition Path Traversal Lenovo System Networking Switch Center Switch Center

7.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.1 HIGH

AV:N/AC:M/Au:N/C:C/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:C/I:N/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Nov 12, 2015 - 03:59 cve.org

HIGH 7.1

DescriptionCVE.org

Race condition in the administration-panel web service in IBM System Networking Switch Center (SNSC) before 7.3.1.5 and Lenovo Switch Center before 8.1.2.0 allows remote attackers to obtain privileged-account access, and consequently provide FileReader.jsp input containing directory traversal sequences to read arbitrary text files, via a request to port 40080 or 40443.

AnalysisAI

Race condition in the administration-panel web service in IBM System Networking Switch Center (SNSC) before 7.3.1.5 and Lenovo Switch Center before 8.1.2.0 allows remote attackers to obtain. Rated high severity (CVSS 7.1), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-362. Race condition in the administration-panel web service in IBM System Networking Switch Center (SNSC) before 7.3.1.5 and Lenovo Switch Center before 8.1.2.0 allows remote attackers to obtain privileged-account access, and consequently provide FileReader.jsp input containing directory traversal sequences to read arbitrary text files, via a request to port 40080 or 40443. Affected products include: Ibm System Networking Switch Center, Lenovo Switch Center. Version information: before 7.3.1.5.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.