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 product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Eve | Lfedge | * | 7.10 (excluding) |
Hard-coded credentials typically create a significant hole that allows an attacker to bypass the authentication that has been configured by the product administrator. This hole might be difficult for the system administrator to detect. Even if detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely. There are two main variations:
In the Inbound variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place. The Outbound variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password which can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product. Any user of that program may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple.