← Übersicht Argo CD

Symlinks in a tar archive allow writing files outside the extraction directory

GHSA-rq7v-q562-vwcq

Hoch · CVSS 8.5 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
20.11.2026 04:49
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact When extracting a tar archive, Argo CD checked each entry's destination path by its text only, without resolving symlinks that earlier entries in the same archive had already created. An archive could create a symlink inside the destination, then a second symlink through it that pointed outside, and then a regular file through that chain. The file was then written to a location of the attacker's choice outside the extraction directory, and extraction reported success. Two components extract archives supplied by the caller: * **repo-server**, through the `GetManifestsWithFiles` API used for local diffs and syncs. Any user who can view an Application, which includes the built-in `role:readonly`, can send an archive. In a standard deployment the repo-server's writable locations are `/tmp` and its mounted volumes, where an attacker can tamper with other Applications' repository checkouts and cached charts. * **Config Management Plugin (CMP) sidecars**, which receive archives from the repo-server. A sidecar usually has a writable filesystem, so a file write there can replace the plugin's own executable and run code with the plugin's credentials on the next manifest generation. All versions from v2.4.0 onward are affected, up to the patched versions below. Archive extraction was introduced in [41db81247](https://github.com/argoproj/argo-cd/commit/41db812474b3f81e02a0ef82761d6d0f006afc34) ([#8600](https://github.com/argoproj/argo-cd/pull/8600)). ### Patches A patch for this vulnerability has been released in the following Argo CD versions: * v3.6.0 (and v3.6.0-rc3) * v3.5.5 * v3.4.11 * v3.3.16 Extraction now goes through Go's `os.Root`, which refuses to write outside the destination directory, and rejects entries whose parent path contains a symlink. ### Workarounds * Restrict who can view Applications (`applications, get`) using [RBAC](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/). The built-in `role:readonly` grants it to every authenticated user by default. * Run the repo-server and CMP sidecars with `readOnlyRootFilesystem: true`, which the default manifests set for the repo-server, so that the only writable locations are temporary volumes. ### Credits The Argo CD team would like to thank @savio-doyensec of Doyensec, in collaboration with @claude and Anthropic Research, for discovering and responsibly disclosing this issue, and @AdamKorcz and @iabdullah215 for independently reporting it. ### References * Fix: [484181673](https://github.com/argoproj/argo-cd/commit/484181673835e1edede6b8652bdd4fc4fd84a917) ([#28881](https://github.com/argoproj/argo-cd/pull/28881)) * Introducing commit: [41db81247](https://github.com/argoproj/argo-cd/commit/41db812474b3f81e02a0ef82761d6d0f006afc34) ([#8600](https://github.com/argoproj/argo-cd/pull/8600)), first released in v2.4.0 ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd/v2kein Fix bekanntGHSA-rq7v-q562-vwcq
Gogithub.com/argoproj/argo-cd/v33.3.16 || >= 3.4.0, 3.4.0 → 3.4.11 || >= 3.5.0, 3.5.0 → 3.6.0-rc3GHSA-rq7v-q562-vwcq

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.