# registry-support: decompress can delete files outside scope via relative paths

Advisory record · `GHSA-84xv-jfrm-h4gm`

- **Identifiers:** `GHSA-84xv-jfrm-h4gm` · `CVE-2024-1485` · `GO-2024-2576`
- **State:** Confirmed
- **Severity:** CVSS 8.0 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-23](https://cwe.mitre.org/data/definitions/23.html) · [CWE-73](https://cwe.mitre.org/data/definitions/73.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 14 Feb 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Feb 2024, 00:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/devfile/registry-support/registry-library` (Go): affected `<0.0.0-20240206`; fixed in `0.0.0-20240206`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go module github.com/devfile/registry-support/registry-library is vulnerable in versions before 0.0.0-20240206. An unauthenticated remote attacker who tricks a user into opening a specially modified .tar archive can cause the decompression cleanup to follow relative paths and overwrite or delete files outside the intended directory. Upgrade to 0.0.0-20240206 or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.0 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:H`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0094, the 61st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-84xv-jfrm-h4gm)

## Sources

- [GitHub Advisory Database: GHSA-84xv-jfrm-h4gm](https://github.com/advisories/GHSA-84xv-jfrm-h4gm)
- [OSV: GHSA-84xv-jfrm-h4gm](https://osv.dev/vulnerability/GHSA-84xv-jfrm-h4gm)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-1485>
- <https://github.com/devfile/registry-support/pull/197>
- <https://github.com/devfile/registry-support/commit/0e44b9ca6d03fac4fc3f77d37656d56dc5defe0d>
- <https://access.redhat.com/security/cve/CVE-2024-1485>
- <https://bugzilla.redhat.com/show_bug.cgi?id=2264106>
- <https://github.com/advisories/GHSA-84xv-jfrm-h4gm>
- <https://github.com/devfile/registry-support>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-84xv-jfrm-h4gm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-84xv-jfrm-h4gm/>. Everything for agents: <https://agentprime.io/llms.txt>.
