CVE-2016-0887 json
EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x and 4.1.x before 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x and 4.1.x before 4.1.3,…
published 2016-04-12 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-0898
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x and 4.1.x before 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x and 4.1.x before 4.1.3, RSA BSAFE Crypto-J before 6.2.1, RSA BSAFE SSL-J before 6.2.1, and RSA BSAFE SSL-C before 2.8.9 allow remote attackers to discover a private-key prime by conducting a Lenstra side-channel attack that leverages an application's failure to detect an RSA signature failure during a TLS session.
Patch / fix
- dell bsafe_crypto-j 6.2.1
- dell bsafe_micro-edition-suite 4.1.5
- dell bsafe_ssl-c 2.8.9
- dell bsafe_ssl-j 6.2.1
Exploit prediction
3.54% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
seclists.org
/bugtraq/2016/Apr/66
mailing-list, third-party-advisory
-
securitytracker.com
/id/1035515
vdb-entry, third-party-advisory
-
securityfocus.com
/archive/1/538055/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1035516
vdb-entry, third-party-advisory
-
packetstormsecurity.com
/files/136656/RSA-BSAFE-Lenstras-Attack.html
third-party-advisory, vdb-entry
-
securitytracker.com
/id/1035517
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-0887
- NVD CVE-2016-0887
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.