Insufficiently protected credentials in LF-Edge, Zededa EVE OS
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-522.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| LF-Edge, Zededa | EVE OS | before 9.5.0 | 9.5.0 | Patch available | CNA |
| — | github.com/lf-edge/eve (Go) | before 0.0.0-20230519072751-977f42b07fa9 | 0.0.0-20230519072751-977f42b07fa9 | Patch available | GHSA-4jvr-vj2c-8q37 |
- EVE OS VendorLF-Edge, Zededa Affected before 9.5.0 Fixed in 9.5.0 Patch available CNA
- github.com/lf-edge/eve (Go) Vendor— Affected before 0.0.0-20230519072751-977f42b07fa9 Fixed in 0.0.0-20230519072751-977f42b07fa9 Patch available GHSA-4jvr-vj2c-8q37
Remediation
- Fix · CNA EVE OS ( LF-Edge, Zededa) Fixed in 9.5.0
- Fix · GHSA-4jvr-vj2c-8q37 github.com/lf-edge/eve (Go) Fixed in 0.0.0-20230519072751-977f42b07fa9 Advisory →
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
LF-Edge, Zededa EVE OS 9.5.0
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2023-23358 Config Partition Not Measured From 2 FrontsPriority LOW 39
Timeline
- 2026-10-02 Threatist record created from CVE-2023-43635
- 2026-10-03 Alias added: GHSA-4jvr-vj2c-8q37
References
More LF-Edge, Zededa vulnerabilities
- TI-2025-34188 eKuiper API endpoints handling SQL queries with user-controlled table names. CVSS 4.0HIGH 8.9
- TI-2024-29055 LF Edge eKuiper has a SQL Injection in sqlKvStore CVSS 3.1HIGH 8.8
- TI-2024-34965 Stored XSS in Configuration Key Functionality CVSS 3.1MEDIUM 6.3
- TI-2024-35324 LF Edge eKuiper has Stored XSS in Rules Functionality CVSS 3.1MEDIUM 5.4
- TI-2023-23360 Freely Allocate Buffer on The Stack With Data From Socket CVSS 3.1CRITICAL 9.9
- TI-2023-23364 Rootfs Not Protected CVSS 3.1HIGH 8.8
Sources
- CVE-2023-43635 · CVE Program
- CVE-2023-43635 · NVD
- FIRST EPSS
- GHSA-4jvr-vj2c-8q37 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences