CVE-2016-8212
First published: Fri Feb 03 2017(Updated: )
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.
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-8212?
CVE-2016-8212 has been rated as medium severity due to its improper OCSP validation vulnerability.
How do I fix CVE-2016-8212?
To fix CVE-2016-8212, upgrade to EMC RSA BSAFE Crypto-J version 6.2.2 or later.
What systems are affected by CVE-2016-8212?
CVE-2016-8212 affects all versions of EMC RSA BSAFE Crypto-J prior to 6.2.2.
What is the impact of CVE-2016-8212 on security?
The impact of CVE-2016-8212 could allow attackers to exploit improper OCSP validation, leading to potential security breaches.
Is there a workaround for CVE-2016-8212?
There is no officially recommended workaround for CVE-2016-8212 other than upgrading to the fixed version.
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/weakness
- agent/author
- agent/severity
- agent/references
- agent/softwarecombine
- agent/type
- 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