CVE-2016-8212

Name: CVE-2016-8212
Creator: NVD / NIST
Published: 2017-02-03T07:59:00.357+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

HIGHCVSS 7.5/10EPSS 1.92%

Last modified Jun 17, 2026

CVE-2016-8212 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2. There is an Improper OCSP Validation Vulnerability. EPSS estimates a 1.92% chance of exploitation in the next 30 days.

Description

An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2. There is an Improper OCSP Validation Vulnerability. OCSP responses have two time values: thisUpdate and nextUpdate. These specify a validity period; however, both values are optional. Crypto-J treats the lack of a nextUpdate as indicating that the OCSP response is valid indefinitely instead of restricting its validity for a brief period surrounding the thisUpdate time. This vulnerability is similar to the issue described in CVE-2015-4748.

Metrics

CVSS 3.1

7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS Probability

1.92%

77.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-404

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: Feb 3, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-8212?

How severe is CVE-2016-8212?

CVE-2016-8212 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 1.92% probability of exploitation in the next 30 days.

How do I fix CVE-2016-8212?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-8212?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST