EVE Doesn't Protect Config Partition with Measured Boot
### Impact Config partition measurement was moved from PCR 13 to PCR 14 in a commit, but PCR 14 was not added to the list of PCRs that seal/unseal the vault key. As a result, an attacker can remove the disk, use another server to modify the files in the config partition, and then re-insert the disk. ### Patches Fixed in EVE version 9.4.3-lts ### Workarounds None (apart from preventing physical access to the device) ### Resources https://help.zededa.com/hc/en-us/articles/43295940828827-TPM-PCR-Index-Security-Implications https://github.com/lf-edge/eve/commit/d9383a7ee4e1c39f5c8c6d4a63cb2ebd00695e8a
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-43634US | high8.8 | — | ||
When sealing/unsealing the “vault” key, a list of PCRs is used, which defines which PCRs
are used.
In a previous project, CYMOTIVE found that the configuration is not protected b… | ||||
references
External citations — patches, advisories, analysis.
- https://asrg.io/security-advisories/config-partition-not-protected-by-measured-bootWEB
- https://asrg.io/security-advisories/cve-2023-43634WEB
- https://github.com/lf-edge/evePACKAGE
- https://github.com/lf-edge/eve/security/advisories/GHSA-wc42-fcjp-v8vqWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-43634ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan