{"vulnerability": "CVE-2023-43637", "sightings": [{"uuid": "3358e6e5-99fe-4f0a-aaa3-39c49ba0bfa3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-43637", "type": "seen", "source": "https://t.me/cibsecurity/70895", "content": "\u203c CVE-2023-43637 \u203c\n\nDue to the implementation of \"deriveVaultKey\", prior to version 7.10, the generated vault keywould always have the last 16 bytes predetermined to be \"arfoobarfoobarfo\".This issue happens because \"deriveVaultKey\" calls \"retrieveCloudKey\" (which will alwaysreturn \"foobarfoobarfoobarfoobarfoobarfo\" as the key), and then merges the 32byterandomly 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 devicesthat were initialized before that and updated to a newer version still have this issue.Roll an update that enforces the full 32bytes key usage.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-09-21T18:31:07.000000Z"}]}