CVE-2022-24730
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedArgo 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceArgo CD versions 1.3.0 through 2.1.10, 2.2.5, and 2.2.x before 2.2.6 contain a path traversal vulnerability combined with improper access control in the `/api/v1/repositories/{repo_url}/appdetails` endpoint. A malicious user with read-only repository access can craft API requests to leak sensitive files from the repo-server, including files from other Applications' source repositories or secrets mounted as files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.3.0, < 2.1.11>= 2.2.0, < 2.2.6= 2.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Argo CD versionRun `argocd version` on the Argo CD server or check the deployed container image tag / Helm chart versionAffected if Version is 1.3.0 through 2.1.10, 2.2.0 through 2.2.5, or 2.3.0
-
Verify the API server is exposedCheck if the Argo CD API server (argocd-server) is running and network-accessible, typically on port 8080 or 443Affected if API server is accessible without proper network restrictions
-
Identify users with read-only repository accessReview Argo CD RBAC configuration in argocd-rbac-cm ConfigMap or external SSO/oidc group mappings for accounts mapped to read-only repo rolesAffected if Any user or service account has read-only access to repositories
-
Confirm repo-server component is runningCheck if the argocd-repo-server pod/service is running in the clusterAffected if Repo-server is deployed and operational
You are affected if your Argo CD version falls within the vulnerable range (1.3.0-2.1.10, 2.2.0-2.2.5, or 2.3.0) and you have users with read-only repository access to the API server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.1.112.2.6
Upgrade Argo CD to version 2.1.11, 2.2.6, or 2.3.0 or later. These versions patch the path traversal vulnerability and add access control checks requiring Application `create` privileges or `get` privileges with an already-used repo_url.
Upgrade to Argo CD version 2.1.11, 2.2.6, or 2.3.0 or later (latest stable 2.x release recommended)
- 1. Identify the current Argo CD version running in the cluster using 'argocd version' CLI or checking the Argo CD namespace in Kubernetes
- 2. Review the Argo CD upgrade documentation for your specific version path (https://argo-cd.readthedocs.io/en/stable/upgrade_guide/)
- 3. Plan the upgrade based on your current version and the fixed releases (2.1.11, 2.2.6, or 2.3.0 or later)
- 4. Backup the Argo CD application resources and any custom configurations
- 5. Execute the upgrade using the appropriate method (Helm upgrade, kubectl apply, or Argo CD operator)
- 6. Verify the Argo CD components are running correctly: 'kubectl get pods -n argocd'
- 7. Confirm the upgraded version: 'argocd version'
- 8. Test that the API endpoint '/api/v1/repositories/{repo_url}/appdetails' no longer returns out-of-bounds file contents
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24730 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24730 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data