Skip to content

← Actionable
Medium, CVSS 6.5

EVE Freely Allocates Buffer on The Stack With Data From Socket

CVE-2023-43632GHSA-6jp5-grgh-jw42

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/lf-edge/eve 0.0.0-20230519072751-977f42b07fa9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
EPSS
  • CVE-2023-43632: 0.66% estimated exploitation activity in the next 30 days; percentile 51.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact VTPM server listens on port 8877, exposing limited TPM functionality. The server reads 4 bytes as a uint32 size header, then allocates that amount on the stack for incoming data. This allows Denial of Service attacks against the vTPM service. An workload (a container or VM) running on EVE-OS can use this to generate a DOS against the vTPM service. Patches Fixed in 9.4.3-lts and 10.1.0 Workarounds None

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6jp5-grgh-jw42

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-43632

Advisory: EVE Freely Allocates Buffer on The Stack With Data From Socket
IDs: CVE-2023-43632, GHSA-6jp5-grgh-jw42
Record: https://patchnext.com/advisories/cve-2023-43632 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lf-edge/eve 0.0.0-20230519072751-977f42b07fa9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lf-edge/eve: affected < 0.0.0-20230519072751-977f42b07fa9; fixed in 0.0.0-20230519072751-977f42b07fa9

## Suggested inspection (read-only)
- Go github.com/lf-edge/eve: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lf-edge/eve.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6jp5-grgh-jw42 (GitHub-reviewed advisory GHSA-6jp5-grgh-jw42 lists affected ranges: Go github.com/lf-edge/eve >=0 <0.0.0-20230519072751-977f42b07fa9)

Commands are suggestions: review each one before running it.

Loading voting…