{"api_version":"1","generated_at":"2026-04-22T23:08:53+00:00","cve":"CVE-2016-8212","urls":{"html":"https://cve.report/CVE-2016-8212","api":"https://cve.report/api/cve/CVE-2016-8212.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2016-8212","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2016-8212"},"summary":{"title":"CVE-2016-8212","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.","state":"PUBLIC","assigner":"security_alert@emc.com","published_at":"2017-02-03 07:59:00","updated_at":"2021-12-15 15:31:00"},"problem_types":["CWE-404"],"metrics":[],"references":[{"url":"http://www.securityfocus.com/archive/1/540066/30/0/threaded","name":"http://www.securityfocus.com/archive/1/540066/30/0/threaded","refsource":"CONFIRM","tags":["Mailing List","Third Party Advisory"],"title":"SecurityFocus","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://www.securityfocus.com/bid/95831","name":"95831","refsource":"BID","tags":["Third Party Advisory","VDB Entry"],"title":"EMC RSA BSAFE Crypto-J Security Bypass and Information Disclosure Vulnerabilities","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"http://www.securitytracker.com/id/1037732","name":"1037732","refsource":"SECTRACK","tags":[],"title":"RSA BSAFE Crypto-J Bugs Let Remote USers Bypass OCSP Time Validation and Conduct Timing Attacks to Determine PKCS MAC Values - SecurityTracker","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8212","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8212","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2016","cve_id":"8212","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"dell","cpe5":"bsafe_crypto-j","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2016","cve_id":"8212","vulnerable":"1","versionEndIncluding":"6.2.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"dell","cpe5":"bsafe_crypto-j","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2016","cve_id":"8212","vulnerable":"1","versionEndIncluding":"6.2.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"emc","cpe5":"rsa_bsafe_crypto-j","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security_alert@emc.com","ID":"CVE-2016-8212","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2","version":{"version_data":[{"version_value":"RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"Improper OCSP Validation Vulnerability"}]}]},"references":{"reference_data":[{"name":"http://www.securityfocus.com/archive/1/540066/30/0/threaded","refsource":"CONFIRM","url":"http://www.securityfocus.com/archive/1/540066/30/0/threaded"},{"name":"95831","refsource":"BID","url":"http://www.securityfocus.com/bid/95831"},{"name":"1037732","refsource":"SECTRACK","url":"http://www.securitytracker.com/id/1037732"}]}},"nvd":{"publishedDate":"2017-02-03 07:59:00","lastModifiedDate":"2021-12-15 15:31:00","problem_types":["CWE-404"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":7.5,"baseSeverity":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":5},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:dell:bsafe_crypto-j:*:*:*:*:*:*:*:*","versionEndExcluding":"6.2.2","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2016","CveId":"8212","Ordinal":"94831","Title":"CVE-2016-8212","CVE":"CVE-2016-8212","Year":"2016"},"notes":[{"CveYear":"2016","CveId":"8212","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2016","CveId":"8212","Ordinal":"2","NoteData":"2017-02-03","Type":"Other","Title":"Published"},{"CveYear":"2016","CveId":"8212","Ordinal":"3","NoteData":"2017-07-24","Type":"Other","Title":"Modified"}]}}}