CVE-2014-6221 json
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…
published 11y ago modified 4mo ago also EUVD-2014-6107
- cvss
- 9.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2014-6221 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.69% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.4 | AV:N/AC:L/Au:N/C:C/I:C/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
www-01.ibm.com
/support/docview.wss?uid=swg21698893
patch, vendor-advisory
-
securityfocus.com
/bid/73915
vdb-entry
-
securitytracker.com
/id/1032026
vdb-entry
Sources
- CVE List CVE-2014-6221
- NVD CVE-2014-6221
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.