CVE-2016-8217
Last modified
CVE-2016-8217 is a low-severity vulnerability rated 3.7/10 on the CVSS scale. EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an integrity MAC for which the password is not known. EPSS estimates a 1.49% chance of exploitation in the next 30 days.
Description
EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an integrity MAC for which the password is not known. An attacker could then feed the modified PKCS#12 file to the toolkit and guess the current MAC one byte at a time. This is possible because Crypto-J uses a non-constant-time method to compare the stored MAC with the calculated MAC. This vulnerability is similar to the issue described in CVE-2015-2601.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Dell | Bsafe Crypto-J | < 6.2.2 |
References
- http://www.securityfocus.com/archive/1/540066/30/0/threadedMailing List, Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/95831Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037732Third Party Advisory, VDB Entry
- http://www.securityfocus.com/archive/1/540066/30/0/threadedMailing List, Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/95831Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037732Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-8217?
How severe is CVE-2016-8217?
How do I fix CVE-2016-8217?
Are you affected by CVE-2016-8217?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
