CVE-2016-8217: Infoleak
First published: Fri Feb 03 2017(Updated: )
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.
Credit: security_alert@emc.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Dell BSAFE Crypto-J | <6.2.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-8217?
CVE-2016-8217 is classified as a medium severity vulnerability due to its potential for timing attacks.
How do I fix CVE-2016-8217?
To fix CVE-2016-8217, you should upgrade to EMC RSA BSAFE Crypto-J version 6.2.2 or later.
What kind of attacks does CVE-2016-8217 facilitate?
CVE-2016-8217 facilitates timing attacks by allowing an attacker to manipulate a PKCS#12 file.
Which versions of software are affected by CVE-2016-8217?
CVE-2016-8217 affects all versions of EMC RSA BSAFE Crypto-J prior to 6.2.2.
What is the main vulnerability in CVE-2016-8217?
The main vulnerability in CVE-2016-8217 is a PKCS#12 timing attack resulting from inadequate MAC integrity handling.
- agent/type
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/weakness
- agent/author
- agent/severity
- agent/references
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/tags
- agent/first-publish-date
- agent/event
- agent/source
- vendor/dell
- canonical/dell bsafe crypto-j