Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-6jp5-grgh-jw42

MEDIUM

GHSA-6jp5-grgh-jw42 is a medium-severity (CVSS 6.5) CWE-789 vulnerability in github.com/lf-edge/eve. O3 Security confirms whether GHSA-6jp5-grgh-jw42 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

EVE Freely Allocates Buffer on The Stack With Data From Socket

Also known asCVE-2023-43632GO-2026-4422
Published
Feb 4, 2026
Updated
Feb 5, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/lf-edge/eve

Real-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

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/lf-edge/eveall versions0.0.0-20230519072751-977f42b07fa9

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/eve. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-6jp5-grgh-jw42 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6jp5-grgh-jw42 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6jp5-grgh-jw42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-6jp5-grgh-jw42 in your dependencies?

O3 detects GHSA-6jp5-grgh-jw42 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-6jp5-grgh-jw42: eve Denial of Service… | O3 Security