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

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

Is there a patch available for CVE-2014-6221?

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

Rational Clearcase CVE-2014-6221

CRITICAL

Cryptographic Issues (CWE-310)

2015-04-06 psirt@us.ibm.com

IBM Information Disclosure Rational Clearcase

9.4

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

9.4 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Apr 06, 2015 - 00:59 cve.org

CRITICAL 9.4

DescriptionCVE.org

The MSCAPI/MSCNG interface implementation in GSKit in IBM Rational ClearCase 7.1.2.x before 7.1.2.17, 8.0.0.x before 8.0.0.14, and 8.0.1.x before 8.0.1.7 does not properly generate random numbers, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via unspecified vectors.

AnalysisAI

The MSCAPI/MSCNG interface implementation in GSKit in IBM Rational ClearCase 7.1.2.x before 7.1.2.17, 8.0.0.x before 8.0.0.14, and 8.0.1.x before 8.0.1.7 does not properly generate random numbers,. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-310. The MSCAPI/MSCNG interface implementation in GSKit in IBM Rational ClearCase 7.1.2.x before 7.1.2.17, 8.0.0.x before 8.0.0.14, and 8.0.1.x before 8.0.1.7 does not properly generate random numbers, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via unspecified vectors. Affected products include: Ibm Rational Clearcase. Version information: before 7.1.2.17.

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.