Attacker Value
Unknown
(0 users assessed)
Exploitability
Unknown
(0 users assessed)
User Interaction
None
Privileges Required
Low
Attack Vector
Local
0

CVE-2023-43637

Disclosure Date: September 21, 2023
Add MITRE ATT&CK tactics and techniques that apply to this CVE.

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.

Add Assessment

No one has assessed this topic. Be the first to add your voice to the community.

CVSS V3 Severity and Metrics
Base Score:
7.8 High
Impact Score:
5.9
Exploitability Score:
1.8
Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector (AV):
Local
Attack Complexity (AC):
Low
Privileges Required (PR):
Low
User Interaction (UI):
None
Scope (S):
Unchanged
Confidentiality (C):
High
Integrity (I):
High
Availability (A):
High

General Information

Vendors

Products

Weaknesses

Additional Info

Technical Analysis