GHSA-84xv-jfrm-h4gm is a high-severity (CVSS 8) Path Traversal vulnerability in github.com/devfile/registry-support/registry-library. A fix is available for github.com/devfile/registry-support/registry-library — see the affected versions and patch details below.
registry-support: decompress can delete files outside scope via relative paths
Exploitation Status
No confirmed exploitation observed yet
- 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-84xv-jfrm-h4gm.
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-84xv-jfrm-h4gm 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 378,567 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/devfile/registry-support/registry-libraryReal-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
A flaw was found in the decompression function of registry-support. This issue can be triggered if an unauthenticated remote attacker tricks a user into parsing a devfile which uses the parent or plugin keywords. This could download a malicious archive and cause the cleanup process to overwrite or delete files outside of the archive, which should not be allowed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/devfile/registry-support/registry-library | all versions | 0.0.0-20240206go get github.com/devfile/registry-support/registry-library@v0.0.0-20240206 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/devfile/registry-support/registry-library, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/devfile/registry-support/registry-library to 0.0.0-20240206 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-84xv-jfrm-h4gm. 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-84xv-jfrm-h4gm in your dependencies?
O3 Security finds GHSA-84xv-jfrm-h4gm across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.