GHSA-phcg-h58r-gmcq
MEDIUMGHSA-phcg-h58r-gmcq is a medium-severity (CVSS 5.2) CWE-328 vulnerability in github.com/lf-edge/eve. O3 Security confirms whether GHSA-phcg-h58r-gmcq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
EVE Doesn't Measure Config Partition From 2 Fronts
Blast Radius
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
Impact
PCR14 is not included in the list of PCRs that seal/unseal the vault key. Additionally, the vault key uses SHA1 PCRs instead of SHA256. Thus an attacker with physical access can take out the disk, use a different computer to modify the files in the /config partition, and re-insert the disk and boot without the change being detected by measured boot and remote attestation.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/lf-edge/eve | all versions | 0.0.0-20230126065759-d9383a7ee4e1 |
Detection & 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. 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.
Fix
Update github.com/lf-edge/eve to 0.0.0-20230126065759-d9383a7ee4e1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-phcg-h58r-gmcq is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-phcg-h58r-gmcq 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-phcg-h58r-gmcq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-phcg-h58r-gmcq in your dependencies?
O3 detects GHSA-phcg-h58r-gmcq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.