GHSA-3mq9-xhgq-r7gj is a medium-severity (CVSS 5.9) CWE-522 vulnerability in github.com/lf-edge/eve. A fix is available for github.com/lf-edge/eve — see the affected versions and patch details below.
EVE: SSH as Root Unlockable Without Triggering Measured Boot
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3mq9-xhgq-r7gj.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-3mq9-xhgq-r7gj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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
On boot, the Pillar container checks for /config/authorized_keys. If present with a valid public key, it enables SSH on port 22 with root login. The /config partition is not protected by measured boot, is mutable and unencrypted.
This enables an attacker with physical access to the device to take out the disk, modify the /config partition using a separate server, then insert it, without the inserted key being flagged as an integrity voilation my measured boot and remote attestation.
Patches
Patched in 9.4.3-lts
Workarounds
None (apart from preventing physical access to the device)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/lf-edge/eve | all versions | 0.0.0-20220708121648-5fef4d92e758go get github.com/lf-edge/eve@v0.0.0-20220708121648-5fef4d92e758 |
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lf-edge/eve to 0.0.0-20220708121648-5fef4d92e758 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mq9-xhgq-r7gj 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3mq9-xhgq-r7gj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3mq9-xhgq-r7gj. 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-3mq9-xhgq-r7gj in your dependencies?
O3 Security finds GHSA-3mq9-xhgq-r7gj across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.