EVE Has Partially Predetermined Vault Key
### Impact The deriveVaultKey function calls retrieveCloudKey which always returns "foobarfoobarfoobarfoobarfoobarfo". When merged with the randomly generated 32-byte key using mergeKeys (16 bytes from each), the last 16 bytes are always "arfoobarfoobarfo". This enables an attacker with physical access to the EVE-OS device to attempt to brute force the remaining 128 bits of key. ### Patches Fixed in 7.10 and 8.12.1-lts ### Workarounds None
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-43637US | high7.8OT elevated | — | ||
Due to the implementation of "deriveVaultKey", prior to version 7.10, the generated vault key
would always have the last 16 bytes predetermined to be "arfoobarfoobarfo".
This iss… | ||||
02
references
External citations — patches, advisories, analysis.
- https://asrg.io/security-advisories/cve-2023-43637WEB
- https://asrg.io/security-advisories/vault-key-partially-predeterminedWEB
- https://github.com/lf-edge/evePACKAGE
- https://github.com/lf-edge/eve/commit/c0c966dc31e2ed9aafc155e6be646adb14756c01WEB
- https://github.com/lf-edge/eve/security/advisories/GHSA-g7vp-j25f-h34pWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-43637ADVISORY
scry
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