CVE-2016-8212
There is an Improper OCSP Validation Vulnerability.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.92%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 1.92% probability · 79th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-404
- Affected
- dell/bsafe crypto-j
- Source
- security_alert@emc.com
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.