[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpPHJ3WBP9Vjzap_vTKQzH2R3vY0F1suRFhHjMA6idG4":3,"g5a-risk:CVE-2016-8217":120},{"success":4,"data":5,"meta":118},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":39,"epssPercentile":26,"epssTimeSeries":40,"severity":41,"affectedProducts":42,"affectedProductsCount":48,"references":49,"referencesCount":70,"weaknesses":71,"weaknessesCount":48,"isActivelyExploited":80,"cisaInfo":26,"otxData":26,"relatedBlogPosts":81,"seoMetadata":82,"configurations":107,"relatedVendorCves":116,"notableEvents":117},"CVE-2016-8217","What is 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.","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#1...","2017-02-03T07:59:00.437","2025-04-20T01:37:25.86",3.7,"CVSS:3.1\u002FAV:N\u002FAC:H\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":29,"CVSSMetricV40":26},[16],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":23,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","NETWORK","HIGH","NONE","UNCHANGED","LOW",null,2.2,1.4,[30],{"Source":17,"Type":18,"CVSSData":31,"BaseSeverity":34,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},{"Version":32,"VectorString":33,"AccessVector":21,"AccessComplexity":34,"Authentication":23,"ConfidentialityImpact":35,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":36,"BaseSeverity":26,"Exploitability":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"CollateralDamagePotential":26,"TargetDistribution":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":26,"EnvironmentalScore":26},"2.0","AV:N\u002FAC:M\u002FAu:N\u002FC:P\u002FI:N\u002FA:N","MEDIUM","PARTIAL",4.3,8.6,2.9,0.01494,[39,39,39,39,39,39,39],"Low",[43],{"vendor":44,"product":45,"version":46,"criteria":47,"vulnerable":4},"dell","bsafe_crypto-j","*","cpe:2.3:a:dell:bsafe_crypto-j:*:*:*:*:*:*:*:*",1,[50,57,60,64,66,68],{"url":51,"source":52,"tags":53},"http:\u002F\u002Fwww.securityfocus.com\u002Farchive\u002F1\u002F540066\u002F30\u002F0\u002Fthreaded","Securityfocus",[54,55,56],"Mailing List","Third Party Advisory","VDB Entry",{"url":58,"source":52,"tags":59},"http:\u002F\u002Fwww.securityfocus.com\u002Fbid\u002F95831",[55,56],{"url":61,"source":62,"tags":63},"http:\u002F\u002Fwww.securitytracker.com\u002Fid\u002F1037732","Securitytracker",[55,56],{"url":51,"source":52,"tags":65},[54,55,56],{"url":58,"source":52,"tags":67},[55,56],{"url":61,"source":62,"tags":69},[55,56],6,[72],{"id":73,"name":74,"description":75,"extendedDescription":76,"status":77,"abstraction":78,"structure":79},"CWE-200","Exposure of Sensitive Information to an Unauthorized Actor","The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.","There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker.  Some kinds of sensitive information include:\nInformation might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected.  These parties include:\nInformation exposures can occur in different ways:\nIt is common practice to describe any loss of confidentiality as an \"information exposure,\" but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read.  CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.","Draft","Class","Simple",false,[],{"title":83,"metaDescription":84,"keywords":85,"canonicalUrl":86,"structuredData":87},"What is CVE-2016-8217? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2016-8217, a low severity cyber security vulnerability from 2017. EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 ...","CVE-2016-8217, CVE-2016-8217 vulnerability, CVE-2016-8217 security, low severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2017, CVSS score, exploit, patch, remediation, dell security, bsafe_crypto-j vulnerability","\u002Fwhat-is\u002Fcve-2016-8217",{"@context":88,"@type":89,"headline":83,"description":84,"datePublished":10,"dateModified":11,"author":90,"publisher":94,"about":98,"mainEntityOfPage":102,"articleSection":105,"keywords":106},"https:\u002F\u002Fschema.org","TechArticle",{"@type":91,"name":92,"url":93},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":91,"name":92,"url":93,"logo":95},{"@type":96,"url":97},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":99,"name":6,"description":100,"additionalType":101},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":103,"@id":104},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2016-8217","Cybersecurity","CVE-2016-8217, CVE-2016-8217 vulnerability, CVE-2016-8217 security, low severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[108],{"Operator":26,"Negate":26,"Nodes":109},[110],{"Operator":111,"Negate":26,"CPEMatch":112},"OR",[113],{"Vulnerable":4,"Criteria":47,"MatchCriteriaID":114,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":115,"VersionEndIncluding":26},"851A69E5-4591-4C1E-8824-1A30F1B885C3","6.2.2",[],[],{"lastModified":11,"cacheTime":119,"version":32},1792265601164,{"score":121,"band":122,"action":123,"scoredAt":124},15,"Info","Track","2026-10-17T08:27:09.261308+00:00"]