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

CVE-2015-5537 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:P/I:N/A:N. EPSS exploitation probability: 0.3%.

Is there a patch available for CVE-2015-5537?

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

Ruggedcom Rox Ii Firmware CVE-2015-5537

MEDIUM

Cleartext Storage of Sensitive Information (CWE-312)

2015-08-03 cve@mitre.org

Siemens Information Disclosure Oracle Ruggedcom Rox Ii Firmware Ruggedcom Rugged Operating System

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Aug 03, 2015 - 01:59 cve.org

MEDIUM 4.3

DescriptionCVE.org

The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566.

AnalysisAI

The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified under CWE-312. The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566. Affected products include: Siemens Ruggedcom Rox Ii Firmware, Siemens Ruggedcom Rugged Operating System. Version information: before 4.2.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.