7.8
High
CVE-2023-43637 Due to the implementation of "deriveVaultKey", prior to version 7.10, the generated vault key would always have the last…
Description
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 issue happens because "deriveVaultKey" calls "retrieveCloudKey" (which will always return "foobarfoobarfoobarfoobarfoobarfo" as the key), and then merges the 32byte randomly generated key with this key (by takeing 16bytes from each, see "mergeKeys"). This makes the key a lot weaker. This issue does not persist in devices that were initialized on/after version 7.10, but devices that were initialized before that and updated to a newer version still have this issue. Roll an update that enforces the full 32bytes key usage.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| EVE OS 7.10 | earliest → < 7.10 | 7.10 |
| edge_virtualization_engine 7.10 | earliest → < 7.10 | 7.10 |
References
- asrg.io asrg.io
Timeline
- Published
- Last modified
Other CVEs of EVE OS
The 8 CVEs of EVE OS →
CVE-2023-43631
On boot, the Pillar eve container checks for the existence and content of
“/config/authorized_keys”
8.8
High
CVE-2023-43632
As noted in the “VTPM.md” file in the eve documentation, “VTPM is a server listening on port 8877 in EVE, exposing…
9.0
Critical
CVE-2023-43633
On boot, the Pillar eve container checks for the existence and content of
“/config/GlobalConfig/global.json”
8.8
High
CVE-2023-43634
When sealing/unsealing the “vault” key, a list of PCRs is used, which defines which PCRs
are used
8.8
High