CVE-2023-43632 — eve
CRITICALCVE-2023-43632 is a critical-severity (CVSS 9) CWE-789 vulnerability in github.com/lf-edge/eve. A fix is available for github.com/lf-edge/eve — see the affected versions and patch details below.
Freely Allocate Buffer on The Stack With Data From Socket
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-43632.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/lf-edge/eveReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
As noted in the “VTPM.md” file in the eve documentation, “VTPM is a server listening on port 8877 in EVE, exposing limited functionality of the TPM to the clients. VTPM allows clients to execute tpm2-tools binaries from a list of hardcoded options” The communication with this server is done using protobuf, and the data is comprised of 2 parts:
-
Header
-
Data
When a connection is made, the server is waiting for 4 bytes of data, which will be the header, and these 4 bytes would be parsed as uint32 size of the actual data to come.
Then, in the function “handleRequest” this size is then used in order to allocate a payload on the stack for the incoming data.
As this payload is allocated on the stack, this will allow overflowing the stack size allocated for the relevant process with freely controlled data.
- An attacker can crash the system.
- An attacker can gain control over the system, specifically on the “vtpm_server” process which has very high privileges.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/lf-edge/eve | all versions | 0.0.0-20230519072751-977f42b07fa9go get github.com/lf-edge/eve@v0.0.0-20230519072751-977f42b07fa9 |
Affected Products
edge virtualization enginelinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/eve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lf-edge/eve to 0.0.0-20230519072751-977f42b07fa9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-43632 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2023-43632 in your dependencies?
Find it across Go, including transitive dependencies.