Vulnerability in Lfedge Eve
CVE-2023-43637
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.
EPSS: 0.001 (3.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H.
Affected products
- Lfedge Eve
- Lf-edge, Zededa Eve Os — versions 0
Weakness classification (CWE)
References
- cve@asrg.io (Third Party Advisory)
Frequently asked questions
- What is CVE-2023-43637?
- CVE-2023-43637 is a high-severity vulnerability in Lfedge Eve, classified under Use of Hard-coded Cryptographic Key. CVSS score: 7.8/10. Published 2023-09-21.
- How severe is CVE-2023-43637?
- High severity. CVSS v3 base score is 7.8 out of 10.