EVE Doesn't Protect Config Partition with Measured Boot

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

EPSS

• CVE-2023-43634: 0.17% estimated exploitation activity in the next 30 days; percentile 6.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Config partition measurement was moved from PCR 13 to PCR 14 in a commit, but PCR 14 was not added to the list of PCRs that seal/unseal the vault key. As a result, an attacker can remove the disk, use another server to modify the files in the config partition, and then re-insert the disk. Patches Fixed in EVE version 9.4.3-lts Workarounds None (apart from preventing physical access to the device) Resources https://help.zededa.com/hc/en-us/articles/43295940828827-TPM-PCR-Index-Security-Implications https://github.com/lf-edge/eve/commit/d9383a7ee4e1c39f5c8c6d4a63cb2ebd00695e8a

Published by the source

4 Feb 2026, 21:38 UTC

Last modified by the source

4 Feb 2026, 21:38 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wc42-fcjp-v8vq

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

# Patch Next advisory brief: CVE-2023-43634

Advisory: EVE Doesn't Protect Config Partition with Measured Boot
IDs: CVE-2023-43634, GHSA-wc42-fcjp-v8vq
Record: https://patchnext.com/advisories/cve-2023-43634 (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 5.9)
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-wc42-fcjp-v8vq (GitHub-reviewed advisory GHSA-wc42-fcjp-v8vq lists affected ranges: Go github.com/lf-edge/eve >=0 <0.0.0-20230519072751-977f42b07fa9)

Commands are suggestions: review each one before running it.