[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fD25tuEC9EVXFCEYhsWzDctVGaHzep5k4KA7fwDpD9u4":3,"g5a-risk:CVE-2023-43635":111},{"success":4,"data":5,"meta":108},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":33,"epssPercentile":26,"epssTimeSeries":34,"severity":35,"affectedProducts":36,"affectedProductsCount":42,"references":43,"referencesCount":42,"weaknesses":48,"weaknessesCount":69,"isActivelyExploited":70,"cisaInfo":26,"otxData":26,"relatedBlogPosts":71,"seoMetadata":72,"configurations":97,"relatedVendorCves":106,"notableEvents":107},"CVE-2023-43635","What is CVE-2023-43635?","Vault Key Sealed With SHA1 PCRs\n\n\n\n\n\n\nThe measured boot solution implemented in EVE OS leans on a PCR locking mechanism.\n\nDifferent parts of the system update different PCR values in the TPM, resulting in a unique\nvalue for each PCR entry.\n\nThese PCRs are then used in order to seal\u002Funseal a key from the TPM which is used to\nencrypt\u002Fdecrypt the “vault” directory.\n\nThis “vault” directory is the most sensitive point in the system and as such, its content should\nbe protected.\n\nThis mechanism is noted in Zededa’s documentation as the “measured boot” mechanism,\ndesigned to protect said “vault”.\n\nThe code that’s responsible for generating and fetching the key from the TPM assumes that\nSHA256 PCRs are used in order to seal\u002Funseal the key, and as such their presence is being\nchecked.\n\nThe issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs.\nThis leads to several issues:\n\n• Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well\nas not sealing their keys at all, meaning the “vault” is not protected from an attacker.\n\n• SHA1 is considered insecure and reduces the complexity level required to unseal the\nkey in machines which have their SHA1 PCRs enabled.\n\n\n\nAn attacker can very easily retrieve the contents of the “vault”, which will effectively render\nthe “measured boot” mechanism meaningless.","Vault Key Sealed With SHA1 PCRs The measured boot solution implemented in EVE OS leans on a PCR locking mechanism. Different parts of the system update diffe...","2023-09-20T15:15:11.987","2023-09-28T06:15:13.07",8.8,"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:C\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":26,"CVSSMetricV40":26},[16,29],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","LOCAL","LOW","NONE","CHANGED","HIGH",null,2,6,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"cve@asrg.io","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},0.00117,[33,33,33,33,33,33,33],"High",[37],{"vendor":38,"product":39,"version":40,"criteria":41,"vulnerable":4},"linuxfoundation","edge_virtualization_engine","*","cpe:2.3:o:linuxfoundation:edge_virtualization_engine:*:*:*:*:*:*:*:*",1,[44],{"url":45,"source":46,"tags":47},"https:\u002F\u002Fasrg.io\u002Fsecurity-advisories\u002Fcve-2023-43635\u002F","Asrg",[],[49,57,63],{"id":50,"name":51,"description":52,"extendedDescription":53,"status":54,"abstraction":55,"structure":56},"CWE-327","Use of a Broken or Risky Cryptographic Algorithm","The product uses a broken or risky cryptographic algorithm or protocol.","Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts.\nIt is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known-insecure algorithm is dangerous because a determined adversary may be able to break the algorithm and compromise whatever data has been protected.\nSince the state of cryptography advances so rapidly, it is common for an algorithm to be considered \"unsafe\" even if it was once thought to be strong. This can happen when new attacks are discovered, or if computing power increases so much that the cryptographic algorithm no longer provides the amount of protection that was originally thought.\nFor a number of reasons, this weakness is even more challenging to manage with hardware deployment of cryptographic algorithms as opposed to software implementation. First, if a flaw is discovered with hardware-implemented cryptography, the flaw cannot be fixed in most cases without a recall of the product, because hardware is not easily replaceable like software. Second, because the hardware product is expected to work for years, the adversary's computing power will only increase over time.","Draft","Class","Simple",{"id":58,"name":59,"description":60,"extendedDescription":61,"status":54,"abstraction":62,"structure":56},"CWE-328","Use of Weak Hash","The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).","A hash function is defined as an algorithm that maps arbitrarily sized data into a fixed-sized digest (output) such that the following properties hold:\nBuilding on this definition, a cryptographic hash function must also ensure that a malicious actor cannot leverage the hash function to have a reasonable chance of success at determining any of the following:\nWhat is regarded as \"reasonable\" varies by context and threat model, but in general, \"reasonable\" could cover any attack that is more efficient than brute force (i.e., on average, attempting half of all possible combinations). Note that some attacks might be more efficient than brute force but are still not regarded as achievable in the real world.\nAny algorithm that does not meet the above conditions will generally be considered weak for general use in hashing.\nIn addition to algorithmic weaknesses, a hash function can be made weak by using the hash in a security context that breaks its security guarantees. For example, using a hash function without a salt for storing passwords (that are sufficiently short) could enable an adversary to create a \"rainbow table\" [REF-637] to recover the password under certain conditions; this attack works against such hash functions as MD5, SHA-1, and SHA-2.","Base",{"id":64,"name":65,"description":66,"extendedDescription":67,"status":68,"abstraction":55,"structure":56},"CWE-522","Insufficiently Protected Credentials","The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and\u002For retrieval.","","Incomplete",3,false,[],{"title":73,"metaDescription":74,"keywords":75,"canonicalUrl":76,"structuredData":77},"What is CVE-2023-43635? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2023-43635, a high severity cyber security vulnerability from 2023. Vault Key Sealed With SHA1 PCRs The measured boot solution ...","CVE-2023-43635, CVE-2023-43635 vulnerability, CVE-2023-43635 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2023, CVSS score, exploit, patch, remediation, linuxfoundation security, edge_virtualization_engine vulnerability","\u002Fwhat-is\u002Fcve-2023-43635",{"@context":78,"@type":79,"headline":73,"description":74,"datePublished":10,"dateModified":11,"author":80,"publisher":84,"about":88,"mainEntityOfPage":92,"articleSection":95,"keywords":96},"https:\u002F\u002Fschema.org","TechArticle",{"@type":81,"name":82,"url":83},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":81,"name":82,"url":83,"logo":85},{"@type":86,"url":87},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":89,"name":6,"description":90,"additionalType":91},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":93,"@id":94},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2023-43635","Cybersecurity","CVE-2023-43635, CVE-2023-43635 vulnerability, CVE-2023-43635 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[98],{"Operator":26,"Negate":26,"Nodes":99},[100],{"Operator":101,"Negate":26,"CPEMatch":102},"OR",[103],{"Vulnerable":4,"Criteria":41,"MatchCriteriaID":104,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":105,"VersionEndIncluding":26},"B3C18178-A893-4EA6-8BBF-51F05CE4CB7E","9.5.0",[],[],{"lastModified":11,"cacheTime":109,"version":110},1792436125741,"2.0",{"score":112,"band":113,"action":114,"scoredAt":115},46,"Medium","Plan remediation","2026-10-16T06:59:11.948655+00:00"]