Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Lfedge | Eve | < 7.10 |
Related Weaknesses (CWE)
References
- https://asrg.io/security-advisories/cve-2023-43637/Third Party Advisory
- https://asrg.io/security-advisories/cve-2023-43637/Third Party Advisory
FAQ
What is CVE-2023-43637?
CVE-2023-43637 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 "...
How severe is CVE-2023-43637?
CVE-2023-43637 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-43637?
Check the references section above for vendor advisories and patch information. Affected products include: Lfedge Eve.