Vault-key brute force via hard-coded key half
Published Sep 21, 2023 · Updated Sep 24, 2024
Hard-coded key material in LF Edge EVE-OS before 7.10 allows physically proximate attackers to brute-force device vault keys. deriveVaultKey passes a constant from retrieveCloudKey to mergeKeys, which replaces half of the random 32-byte TPM key with fixed bytes. Exposure requires physical access and low privileges, and persists on devices initialized before 7.10 even after a later upgrade.
Summary
What happened
Hard-coded key material in LF Edge EVE-OS before 7.10 allows physically proximate attackers to brute-force device vault keys. deriveVaultKey passes a constant from retrieveCloudKey to mergeKeys, which replaces half of the random 32-byte TPM key with fixed bytes. Exposure requires physical access and low privileges, and persists on devices initialized before 7.10 even after a later upgrade.
The record
- CVE
- CVE-2023-43637
- Published
- Sep 21, 2023
- Updated
- Sep 24, 2024
- Vendor
- Linux Foundation
- Product
- EVE (Edge Virtualization Engine)
- Classifications
- CWE-321, CAPEC-115, T1110
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo