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 b
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Apr 5, 2015
- Updated
- Jun 16, 2026
- EPSS
- 2.7% · 85th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 37 / 40 · 9.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | rational clearcase | cpe:2.3:a:ibm:rational_clearcase |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm rational clearcase7.1.2
- ibm rational clearcase7.1.2.1
- ibm rational clearcase7.1.2.10
- ibm rational clearcase7.1.2.11
- ibm rational clearcase7.1.2.12
- ibm rational clearcase7.1.2.13
- ibm rational clearcase7.1.2.14
- ibm rational clearcase7.1.2.15
- ibm rational clearcase7.1.2.16
- ibm rational clearcase7.1.2.2
- ibm rational clearcase7.1.2.3
- ibm rational clearcase7.1.2.4
- ibm rational clearcase7.1.2.5
- ibm rational clearcase7.1.2.6
- ibm rational clearcase7.1.2.7
- ibm rational clearcase7.1.2.9
- ibm rational clearcase8.0.0
- ibm rational clearcase8.0.0.1
- ibm rational clearcase8.0.0.10
- ibm rational clearcase8.0.0.11
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-4059IBM Rational ClearCase 1.0.0.0 GIT connector does not sufficiently protect the document database password.40Plan
- CVE-2014-0931Multiple XML external entity (XXE) vulnerabilities in the (1) CCRC WAN Server / CM Server, (2) Perl CC/CQ integration trigger scripts, (3) C37Monitor
- CVE-2015-5039The Remote Client and change management integrations in IBM Rational ClearCase 7.1.x, 8.0.0.x before 8.0.0.18, and 8.0.1.x before 8.0.1.11 d29Monitor
- CVE-2013-5416Unspecified vulnerability in IBM Rational ClearCase through 7.1.2.12, 8.0.0.x before 8.0.0.9, and 8.0.1.x before 8.0.1.2 allows local users 28Monitor
- CVE-2013-5415Buffer overflow in IBM Rational ClearCase through 7.1.2.12, 8.0.0.x before 8.0.0.9, and 8.0.1.x before 8.0.1.2 allows local users to gain pr28Monitor
- CVE-2013-5373The RemoteClient component in IBM Rational ClearCase 8.0.0.03 through 8.0.0.07, and 8.0.1, uses world-writable permissions for the rcleartoo27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www-01.ibm.com/support/docview.wss?uid=swg21698893
- www.securityfocus.com/bid/73915
- www.securitytracker.com/id/1032026
Vendor advisories and official records. Exploit/PoC links are deliberately left out.