Summary
Fixed in 7.10 and 8.12.1-lts
Workarounds
None
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.
Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.
CVE-2023-43637 has a CVSS score of 6.7 (Medium). The vector is requires physical access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20220310190112-c0c966dc31e2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2023-43637? CVE-2023-43637 is a medium-severity use of hard-coded credentials vulnerability in github.com/lf-edge/eve (go), affecting versions < 0.0.0-20220310190112-c0c966dc31e2. It is fixed in 0.0.0-20220310190112-c0c966dc31e2. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
- How severe is CVE-2023-43637? CVE-2023-43637 has a CVSS score of 6.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/lf-edge/eve are affected by CVE-2023-43637? github.com/lf-edge/eve (go) versions < 0.0.0-20220310190112-c0c966dc31e2 is affected.
- Is there a fix for CVE-2023-43637? Yes. CVE-2023-43637 is fixed in 0.0.0-20220310190112-c0c966dc31e2. Upgrade to this version or later.
- Is CVE-2023-43637 exploitable, and should I be worried? Whether CVE-2023-43637 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-43637 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-43637? Upgrade
github.com/lf-edge/eveto 0.0.0-20220310190112-c0c966dc31e2 or later.