ASRGVULNRICHMENT:CVE-2023-43637CVE-2023-43637 Vault Key Partially Predetermined
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
AI Score
Confidence
Low
SSVC
Exploitation
none
Automatable
no
Technical Impact
total
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.
ADP Affected
[
{
"cpes": [
"cpe:2.3:o:linuxfoundation:edge_virtualization_engine:*:*:*:*:*:*:*:*"
],
"vendor": "linuxfoundation",
"product": "edge_virtualization_engine",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "7.10",
"versionType": "custom"
}
],
"defaultStatus": "unknown"
}
]Related
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
AI Score
Confidence
Low
SSVC
Exploitation
none
Automatable
no
Technical Impact
total