Skip to content
Fencer Intel
high 8.8

CVE-2023-43634 json

Config Partition Not Protected by Measured Boot

published 3y ago modified 4mo ago also GHSA-wc42-fcjp-v8vq , GO-2026-4432 , EUVD-2023-48034

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

When sealing/unsealing the “vault” key, a list of PCRs is used, which defines which PCRs are used.

In a previous project, CYMOTIVE found that the configuration is not protected by the secure boot, and in response Zededa implemented measurements on the config partition that was mapped to PCR 13.

In that process, PCR 13 was added to the list of PCRs that seal/unseal the key.

In commit “56e589749c6ff58ded862d39535d43253b249acf”, the config partition measurement moved from PCR 13 to PCR 14, but PCR 14 was not added to the list of PCRs that seal/unseal the key.

This change makes the measurement of PCR 14 effectively redundant as it would not affect the sealing/unsealing of the key.

An attacker could modify the config partition without triggering the measured boot, this could result in the attacker gaining full control over the device with full access to the contents of the encrypted “vault”

Patch / fix

  • go github.com/lf-edge/eve 0.0.0-20230519072751-977f42b07fa9
  • LF-Edge, Zededa EVE OS 8.6.0, 9.5.0
  • lfedge eve 8.6.0, 9.5.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260205T172317-150000.1.146.1

suse advisories SUSE-SU-2026:0403-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2023-43634 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 5.9 CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/lf-edge/eve
<0.0.0-20230519072751-977f42b07fa9
0.0.0-20230519072751-977f42b07fa9

Affected products

  • LF-Edge, Zededa EVE OS
  • lfedge eve

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-922 Insecure Storage of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.