Skip to content
Fencer Intel
medium 4.3

CVE-2022-24904 json

Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

published 4y ago modified 19d ago also GHSA-6gcg-hp2x-q54h , GO-2022-0453 , EUVD-2022-2791

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.1.15, 2.2.9, 2.3.4
  • argoproj argo_cd 2.1.15, 2.2.9, 2.3.4

Is CVE-2022-24904 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-24904 updated cvss 4.3

argocd: Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

  • Red Hat OpenShift GitOps 1.3 openshift-gitops-1/dex-rhel8 v1.3.9-3, openshift-gitops-1/dex-rhel8 v1.3.10-1, openshift-gitops-1/argocd-rhel8 v1.3.9-3, openshift-gitops-1/gitops-rhel8 v1.3.9-3, openshift-gitops-1/argocd-rhel8 v1.3.10-1, openshift-gitops-1/gitops-rhel8 v1.3.10-1, +8 more
    fixed: vendor fix RHSA-2022:4671
  • Red Hat OpenShift GitOps 1.4 openshift-gitops-1/dex-rhel8 v1.4.7-2, openshift-gitops-1/argocd-rhel8 v1.4.7-2, openshift-gitops-1/gitops-rhel8 v1.4.7-2, openshift-gitops-1/kam-delivery-rhel8 v1.4.7-2, openshift-gitops-1/applicationset-rhel8 v1.4.7-2, openshift-gitops-1/gitops-rhel8-operator v1.4.7-2, +1 more
    fixed: vendor fix RHSA-2022:4692
  • Red Hat OpenShift GitOps 1.5 openshift-gitops-1/dex-rhel8 v1.5.1-4, openshift-gitops-1/argocd-rhel8 v1.5.1-4, openshift-gitops-1/gitops-rhel8 v1.5.1-4, openshift-gitops-1/kam-delivery-rhel8 v1.5.1-4, openshift-gitops-1/applicationset-rhel8 v1.5.1-4, openshift-gitops-1/gitops-rhel8-operator v1.5.1-4, +1 more
    fixed: vendor fix RHSA-2022:4690

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
<2.1.15
>=2.2.0, <2.2.9
>=2.3.0, <2.3.4
2.1.15
2.2.9
2.3.4
go github.com/argoproj/argo-cd
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-61 UNIX Symbolic Link (Symlink) Following
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.