CVE-2023-43635
published 2023-09-20CVE-2023-43635: 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…
PriorityP343high8.8CVSS 3.1
AVLACLPRLUINSCCHIHAH
EPSS
0.11%
1.5th percentile
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 different PCR values in the TPM, resulting in a unique
value for each PCR entry.
These PCRs are then used in order to seal/unseal a key from the TPM which is used to
encrypt/decrypt the “vault” directory.
This “vault” directory is the most sensitive point in the system and as such, its content should
be protected.
This mechanism is noted in Zededa’s documentation as the “measured boot” mechanism,
designed to protect said “vault”.
The code that’s responsible for generating and fetching the key from the TPM assumes that
SHA256 PCRs are used in order to seal/unseal the key, and as such their presence is being
checked.
The issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs.
This leads to several issues:
• Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well
as not sealing their keys at all, meaning the “vault” is not protected from an attacker.
• SHA1 is considered insecure and reduces the complexity level required to unseal the
key in machines which have their SHA1 PCRs enabled.
An attacker can very easily retrieve the contents of the “vault”, which will effectively render
the “measured boot” mechanism meaningless.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | lf-edge_eve | >= 0 < 0.0.0-20230519072751-977f42b07fa9 | 0.0.0-20230519072751-977f42b07fa9 |
| lf-edge_zededa | eve_os | < 9.5.0 | 9.5.0 |
| linuxfoundation | edge_virtualization_engine | < 9.5.0 | 9.5.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
EVE Seals Vault Key With SHA1 PCRs in github.com/lf-edge/eve
osv·2026-02-17
CVE-2023-43635 EVE Seals Vault Key With SHA1 PCRs in github.com/lf-edge/eve
EVE Seals Vault Key With SHA1 PCRs in github.com/lf-edge/eve
EVE Seals Vault Key With SHA1 PCRs in github.com/lf-edge/eve
GHSA
EVE Seals Vault Key With SHA1 PCRs
ghsa·2026-02-04
CVE-2023-43635 [MEDIUM] CWE-327 EVE Seals Vault Key With SHA1 PCRs
EVE Seals Vault Key With SHA1 PCRs
### Impact
The vault key is sealed using SHA1 PCRs instead of SHA256 PCRs
Thus an attacker with physical access to an EVE-OS device can try to brute force creating a kernel or rootfs image which produces the same SHA1 PCR but with malicious content.
### Patches
Fixed in 9.4.3-lts and 10.1.0
### Workarounds
None
OSV
EVE Seals Vault Key With SHA1 PCRs
osv·2026-02-04
CVE-2023-43635 [MEDIUM] EVE Seals Vault Key With SHA1 PCRs
EVE Seals Vault Key With SHA1 PCRs
### Impact
The vault key is sealed using SHA1 PCRs instead of SHA256 PCRs
Thus an attacker with physical access to an EVE-OS device can try to brute force creating a kernel or rootfs image which produces the same SHA1 PCR but with malicious content.
### Patches
Fixed in 9.4.3-lts and 10.1.0
### Workarounds
None
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2023-09-20
Published