CVE-2023-43637 json
Vault Key Partially Predetermined
published 3y ago modified 4mo ago also GHSA-g7vp-j25f-h34p , GO-2026-4436 , EUVD-2023-48037
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/lf-edge/eve 0.0.0-20220310190112-c0c966dc31e2
- LF-Edge, Zededa EVE OS 7.10
- linuxfoundation edge_virtualization_engine 7.10
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1
suse advisories SUSE-SU-2026:0757-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2023-43637 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 6.7 | CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/lf-edge/eve | <0.0.0-20220310190112-c0c966dc31e2 |
0.0.0-20220310190112-c0c966dc31e2 |
Affected products
- LF-Edge, Zededa EVE OS
- linuxfoundation edge_virtualization_engine
Classification
References
-
github.com
/lf-edge/eve/commit/c0c966dc31e2ed9aafc155e6be646adb14756c01
web, patch
-
asrg.io
/security-advisories/cve-2023-43637/
third-party-advisory
-
github.com
/lf-edge/eve/security/advisories/GHSA-g7vp-j25f-h34p
web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-43637
advisory
-
asrg.io
/security-advisories/cve-2023-43637
web
-
asrg.io
/security-advisories/vault-key-partially-predetermined
web
-
github.com
/lf-edge/eve
package
Sources
- CVE List CVE-2023-43637
- GitHub Advisory GHSA-g7vp-j25f-h34p
- NVD CVE-2023-43637
- OSV GO-2026-4436
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.