[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fRuTxaq9OAaqNx5tyDovy8uHToN0dQLPi4PojMakUPTg":3,"g5a-risk:CVE-2010-2450":135},{"success":4,"data":5,"meta":133},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":55,"references":56,"referencesCount":55,"weaknesses":71,"weaknessesCount":87,"isActivelyExploited":88,"cisaInfo":26,"otxData":26,"relatedBlogPosts":89,"seoMetadata":90,"configurations":115,"relatedVendorCves":131,"notableEvents":132},"CVE-2010-2450","What is CVE-2010-2450?","The keygen.sh script in Shibboleth SP 2.0 (located in \u002Fusr\u002Flocal\u002Fetc\u002Fshibboleth by default) uses OpenSSL to create a DES private key which is placed in sp-key.pm. It relies on the root umask (default 22) instead of chmoding the resulting file itself, so the generated private key is world readable by default.","The keygen.sh script in Shibboleth SP 2.0 (located in \u002Fusr\u002Flocal\u002Fetc\u002Fshibboleth by default) uses OpenSSL to create a DES private key which is placed in sp-ke...","2019-11-07T21:15:10.317","2019-11-13T18:48:39.433",7.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\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","LOW","NONE","UNCHANGED","HIGH",null,3.9,3.6,[30],{"Source":17,"Type":18,"CVSSData":31,"BaseSeverity":36,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},{"Version":32,"VectorString":33,"AccessVector":21,"AccessComplexity":22,"Authentication":23,"ConfidentialityImpact":34,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":35,"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:L\u002FAu:N\u002FC:P\u002FI:N\u002FA:N","PARTIAL",5,"MEDIUM",10,2.9,0.012,[39,39,39,39,39,39,39],"High",[43,47,52],{"vendor":44,"product":45,"version":32,"criteria":46,"vulnerable":4},"shibboleth","service_provider","cpe:2.3:a:shibboleth:service_provider:2.0:*:*:*:*:*:*:*",{"vendor":48,"product":49,"version":50,"criteria":51,"vulnerable":4},"debian","debian_linux","8.0","cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*",{"vendor":48,"product":49,"version":53,"criteria":54,"vulnerable":4},"9.0","cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*",3,[57,64,67],{"url":58,"source":59,"tags":60},"https:\u002F\u002Fbugs.debian.org\u002Fcgi-bin\u002Fbugreport.cgi?bug=571631","Debian",[61,62,63],"Mailing List","Patch","Third Party Advisory",{"url":65,"source":59,"tags":66},"https:\u002F\u002Fsecurity-tracker.debian.org\u002Ftracker\u002FCVE-2010-2450",[63],{"url":68,"source":69,"tags":70},"https:\u002F\u002Ftodos.internet2.edu\u002Fbrowse\u002FSSPCPP-106","Internet2",[63],[72,80],{"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",{"id":81,"name":82,"description":83,"extendedDescription":84,"status":85,"abstraction":86,"structure":79},"CWE-916","Use of Password Hash With Insufficient Computational Effort","The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.","Many password storage mechanisms compute a hash and store the hash, instead of storing the original password in plaintext. In this design, authentication involves accepting an incoming password, computing its hash, and comparing it to the stored hash.\nMany hash algorithms are designed to execute quickly with minimal overhead, even cryptographic hashes. However, this efficiency is a problem for password storage, because it can reduce an attacker's workload for brute-force password cracking. If an attacker can obtain the hashes through some other method (such as SQL injection on a database that stores hashes), then the attacker can store the hashes offline and use various techniques to crack the passwords by computing hashes efficiently. Without a built-in workload, modern attacks can compute large numbers of hashes, or even exhaust the entire space of all possible passwords, within a very short amount of time, using massively-parallel computing (such as cloud computing) and GPU, ASIC, or FPGA hardware. In such a scenario, an efficient hash algorithm helps the attacker.\nThere are several properties of a hash scheme that are relevant to its strength against an offline, massively-parallel attack:\nNote that the security requirements for the product may vary depending on the environment and the value of the passwords. Different schemes might not provide all of these properties, yet may still provide sufficient security for the environment. Conversely, a solution might be very strong in preserving one property, which still being very weak for an attack against another property, or it might not be able to significantly reduce the efficiency of a massively-parallel attack.","Incomplete","Base",2,false,[],{"title":91,"metaDescription":92,"keywords":93,"canonicalUrl":94,"structuredData":95},"What is CVE-2010-2450? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2010-2450, a high severity cyber security vulnerability from 2019. The keygen.sh script in Shibboleth SP 2.0 (located in \u002Fusr\u002Fl...","CVE-2010-2450, CVE-2010-2450 vulnerability, CVE-2010-2450 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2019, CVSS score, exploit, patch, remediation, shibboleth security, debian security, service_provider vulnerability, debian_linux vulnerability","\u002Fwhat-is\u002Fcve-2010-2450",{"@context":96,"@type":97,"headline":91,"description":92,"datePublished":10,"dateModified":11,"author":98,"publisher":102,"about":106,"mainEntityOfPage":110,"articleSection":113,"keywords":114},"https:\u002F\u002Fschema.org","TechArticle",{"@type":99,"name":100,"url":101},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":99,"name":100,"url":101,"logo":103},{"@type":104,"url":105},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":107,"name":6,"description":108,"additionalType":109},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":111,"@id":112},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2010-2450","Cybersecurity","CVE-2010-2450, CVE-2010-2450 vulnerability, CVE-2010-2450 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[116,123],{"Operator":26,"Negate":26,"Nodes":117},[118],{"Operator":119,"Negate":26,"CPEMatch":120},"OR",[121],{"Vulnerable":4,"Criteria":46,"MatchCriteriaID":122,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"70EBED43-4EED-41E6-8E80-F05EBA42A2BE",{"Operator":26,"Negate":26,"Nodes":124},[125],{"Operator":119,"Negate":26,"CPEMatch":126},[127,129],{"Vulnerable":4,"Criteria":51,"MatchCriteriaID":128,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"C11E6FB0-C8C0-4527-9AA0-CB9B316F8F43",{"Vulnerable":4,"Criteria":54,"MatchCriteriaID":130,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"DEECE5FC-CACF-4496-A3E7-164736409252",[],[],{"lastModified":11,"cacheTime":134,"version":32},1792443158219,{"score":136,"band":137,"action":138,"scoredAt":139},47,"Medium","Plan remediation","2026-10-16T06:47:12.633432+00:00"]