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.
The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Eve | Lfedge | * | 7.10 (excluding) |