Skip to content
Fencer Intel
high 7.7

CVE-2022-24730 json

Path traversal and improper access control allows leaking out-of-bound files from Argo CD repo-server

published 4y ago modified 4mo ago also GHSA-r9cr-hvjj-496v , GO-2022-0357 , EUVD-2022-1529

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

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 1.3.0 but before versions 2.1.11, 2.2.6, and 2.3.0 is vulnerable to a path traversal bug, compounded by an improper access control bug, allowing a malicious user with read-only repository access to leak sensitive files from Argo CD's repo-server. A malicious Argo CD user who has been granted `get` access for a repository containing a Helm chart can craft an API request to the `/api/v1/repositories/{repo_url}/appdetails` endpoint to leak the contents of out-of-bounds files from the repo-server. The malicious payload would reference an out-of-bounds file, and the contents of that file would be returned as part of the response. Contents from a non-YAML file may be returned as part of an error message. The attacker would have to know or guess the location of the target file. Sensitive files which could be leaked include files from other Applications' source repositories or any secrets which have been mounted as files on the repo-server. This vulnerability is patched in Argo CD versions 2.1.11, 2.2.6, and 2.3.0. The patches prevent path traversal and limit access to users who either A) have been granted Application `create` privileges or B) have been granted Application `get` privileges and are requesting details for a `repo_url` that has already been used for the given Application. There are currently no known workarounds.

Patch / fix

  • go github.com/argoproj/argo-cd 2.1.11, 2.2.6, 2.3.0
  • go github.com/argoproj/argo-cd/v2 2.1.11, 2.2.6, 2.3.0
  • argoproj argo_cd 2.1.11, 2.2.6

Is CVE-2022-24730 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-24730 updated cvss 7.7

argocd: path traversal and improper access control allows leaking out-of-bound files

  • Red Hat OpenShift GitOps 1.2 openshift-gitops-1/argocd-rhel8 v1.2.3-3
    fixed: vendor fix RHSA-2022:1039
  • Red Hat OpenShift GitOps 1.3 openshift-gitops-1/argocd-rhel8 v1.3.5-4, openshift-gitops-1/argocd-rhel8 v1.3.6-3
    fixed: vendor fix RHSA-2022:1040
  • Red Hat OpenShift GitOps 1.4 openshift-gitops-1/argocd-rhel8 v1.4.4-6
    fixed: vendor fix RHSA-2022:1041
  • Red Hat OpenShift GitOps 1.2 openshift-gitops-1/gitops-rhel8 v1.2.3-3, openshift-gitops-1/kam-delivery-rhel8 v1.2.3-3, openshift-gitops-1/applicationset-rhel8 v1.2.3-3, openshift-gitops-1/gitops-rhel8-operator v1.2.3-3, openshift-gitops-1/gitops-operator-bundle v1.2.3-3 Red Hat OpenShift GitOps 1.3 openshift-gitops-1/dex-rhel8 v1.3.5-4, openshift-gitops-1/dex-rhel8 v1.3.6-3, openshift-gitops-1/gitops-rhel8 v1.3.5-4, openshift-gitops-1/gitops-rhel8 v1.3.6-3, openshift-gitops-1/kam-delivery-rhel8 v1.3.5-4, openshift-gitops-1/kam-delivery-rhel8 v1.3.6-3, +6 more Red Hat OpenShift GitOps 1.4 openshift-gitops-1/dex-rhel8 v1.4.4-6, openshift-gitops-1/gitops-rhel8 v1.4.4-6, openshift-gitops-1/kam-delivery-rhel8 v1.4.4-6, openshift-gitops-1/applicationset-rhel8 v1.4.4-6, openshift-gitops-1/gitops-rhel8-operator v1.4.4-6, openshift-gitops-1/gitops-operator-bundle v1.4.4-6
    not affected: vulnerable code not present

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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd
>=1.3.0, <2.1.11
>=2.2.0, <2.2.6
>=2.3.0-rc1, <2.3.0
>=1.3.0
2.1.11
2.2.6
2.3.0
go github.com/argoproj/argo-cd/v2
<2.1.11
>=2.2.0, <2.2.6
>=2.3.0-rc1, <2.3.0
2.1.11
2.2.6
2.3.0

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
  • CWE-284 Improper Access Control
  • CWE-863 Incorrect Authorization

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.