Skip to content

EVE Has Partially Predetermined Vault Key

Moderate severity GitHub Reviewed Published Feb 4, 2026 in lf-edge/eve • Updated Feb 4, 2026

Package

gomod github.com/lf-edge/eve (Go)

Affected versions

< 0.0.0-20220310190112-c0c966dc31e2

Patched versions

0.0.0-20220310190112-c0c966dc31e2

Description

Impact

The deriveVaultKey function calls retrieveCloudKey which always returns "foobarfoobarfoobarfoobarfoobarfo". When merged with the randomly generated 32-byte key using mergeKeys (16 bytes from each), the last 16 bytes are always "arfoobarfoobarfo". This enables an attacker with physical access to the EVE-OS device to attempt to brute force the remaining 128 bits of key.

Patches

Fixed in 7.10 and 8.12.1-lts

Workarounds

None

References

@eriknordmark eriknordmark published to lf-edge/eve Feb 4, 2026
Published to the GitHub Advisory Database Feb 4, 2026
Reviewed Feb 4, 2026
Last updated Feb 4, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Physical
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(7th percentile)

Weaknesses

Use of Hard-coded Cryptographic Key

The product uses a hard-coded, unchangeable cryptographic key. Learn more on MITRE.

Use of Hard-coded Credentials

The product contains hard-coded credentials, such as a password or cryptographic key. Learn more on MITRE.

CVE ID

CVE-2023-43637

GHSA ID

GHSA-g7vp-j25f-h34p

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.