CVE-2016-8217 Information disclosure in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2

Low 3.7 Published Updated

An attacker can guess PKCS#12 MAC bytes via timing attacks due to non-constant-time comparisons, potentially exposing integrity checks.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2016-8217?

CVE-2016-8217 is a low-severity vulnerability in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2, published on 3 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-200

Which versions are affected by CVE-2016-8217?

It affects 1 product.

Products include Dell Bsafe Crypto-J.

How do I fix CVE-2016-8217?

No fix has been published for CVE-2016-8217 yet. Limit exposure of the affected software until one is available.

Is CVE-2016-8217 being exploited?

There is no known exploitation of CVE-2016-8217 in the wild and no public exploit code.

Sources

Also known as GHSA-34fw-m7m3-5c57.

Is CVE-2016-8217 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free