CVE & CISA-KEV Catalog

CVE-2016-8212

HIGHEPSS 78th pctl
7.5
CVSS v3
NVD

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.

How to fix

Remediation Available
bsafe crypto-jNVD
Affected:< 6.2.2Fixed in:6.2.2CVE-2016-8212derived from NVD

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

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

Exploit Intelligence

1.92%probability of exploitation in 30 days
78thpercentile

Elevated risk: more likely to be exploited than 78% of all known CVEs.

References

Related Vulnerabilities

Other CWE-404 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2022-44267Medium6.577%-Fix
CVE-2018-8120High7.074%KEV + Ransom-
CVE-2018-8210High7.824%--
CVE-2018-8639High7.822%KEV + Ransom-
CVE-2023-3206Medium5.319%--
CVE-2018-8450High8.816%--

Common questions

How do I fix CVE-2016-8212?

Upgrade bsafe crypto-j to 6.2.2 or later.

Is CVE-2016-8212 being actively exploited?

Not that we know of. CVE-2016-8212 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.9% is the estimated probability that it will be exploited in the next 30 days. That is higher than 78% of all scored CVEs.

How severe is CVE-2016-8212?

CVE-2016-8212 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2016-8212 affect?

Published advisories record a fix for bsafe crypto-j (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2016-8212
CVE-2016-8212 severity badge

Markdown

[![CVE-2016-8212](https://tridentstack.com/cve/badge/CVE-2016-8212.svg)](https://tridentstack.com/cve/CVE-2016-8212)

HTML

<a href="https://tridentstack.com/cve/CVE-2016-8212"><img src="https://tridentstack.com/cve/badge/CVE-2016-8212.svg" alt="CVE-2016-8212"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-13.