cve,link,title,description,vendor,products,score,severity,epss,cisa,cisa_published,article,ransomware,exploited,exploited_date,poc,trended,trended_no_1,trended_no_1_date,published,trended_score
CVE-2016-8217,https://securityvulnerability.io/vulnerability/CVE-2016-8217,,EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an integrity MAC for which the password is not known. An attacker could then feed the modified PKCS#12 file to the toolkit and guess the current MAC one byte at a time. This is possible because Crypto-J uses a non-constant-time method to compare the stored MAC with the calculated MAC. This vulnerability is similar to the issue described in CVE-2015-2601.,Dell,Rsa Bsafe Crypto-j Rsa Bsafe Crypto-j Versions Prior To 6.2.2,3.7,LOW,0.0017999999690800905,false,,false,false,false,,,false,false,,2017-02-03T07:24:00.000Z,0
CVE-2016-8212,https://securityvulnerability.io/vulnerability/CVE-2016-8212,,"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.",Dell,Rsa Bsafe Crypto-j Rsa Bsafe Crypto-j Versions Prior To 6.2.2,7.5,HIGH,0.002099999925121665,false,,false,false,false,,,false,false,,2017-02-03T07:24:00.000Z,0