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

High 7.7 Published Updated

A malicious user with read-only repository access can exploit path traversal and improper access control to leak sensitive files from the Argo CD repo-server.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2022-24730?

CVE-2022-24730 is a high-severity path traversal vulnerability in Argoproj Argo Cd, published on 23 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-863, CWE-284, CWE-22

Which versions are affected by CVE-2022-24730?

8 open source packages ship an affected version, including github.com/argoproj/argo-cd and github.com/argoproj/argo-cd/v2. It affects 1 product.

PackageAffectedFixed in
github.com/argoproj/argo-cd GoFrom 1.3.0None
github.com/argoproj/argo-cd GoFrom 1.3.02.1.11
github.com/argoproj/argo-cd GoFrom 1.3.02.1.11
github.com/argoproj/argo-cd GoFrom 2.2.02.2.6
github.com/argoproj/argo-cd GoFrom 2.2.02.2.6
github.com/argoproj/argo-cd GoFrom 2.3.0-rc12.3.0
2 more packages
github.com/argoproj/argo-cd GoFrom 2.3.0-rc12.3.0
github.com/argoproj/argo-cd/v2 GoAll versions2.1.11, 2.2.6, 2.3.0

Products include Argoproj Argo Cd.

How do I fix CVE-2022-24730?

Upgrade github.com/argoproj/argo-cd to a fixed version for your release line: 2.1.11, 2.2.6 or 2.3.0.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2022-24730 being exploited?

There is no known exploitation of CVE-2022-24730 in the wild and no public exploit code.

All Argoproj Argo Cd vulnerabilities

Sources

Also known as GHSA-r9cr-hvjj-496v, GO-2022-0357.

Is CVE-2022-24730 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free