# CVE-2023-40584: Denial of Service to Argo CD repo-server > A malicious user can cause a denial of service in Argo CD repo-server by uploading a crafted tar.gz archive that exploits unvalidated file sizes and permissions. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Sep 2023 - **Updated:** 26 Sep 2024 - **Also known as:** BIT-argo-cd-2023-40584, GHSA-g687-f2gx-6wm8, GO-2023-2050 ## What is CVE-2023-40584? CVE-2023-40584 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 7 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Argo CD is a declarative continuous deployment for Kubernetes. All versions of ArgoCD starting from v2.4 have a bug where the ArgoCD repo-server component is vulnerable to a Denial-of-Service attack vector. Specifically, the said component extracts a user-controlled tar.gz file without validating the size of its inner files. As a result, a malicious, low-privileged user can send a malicious tar.gz file that exploits this vulnerability to the repo-server, thereby harming the system's functionality and availability. Additionally, the repo-server is susceptible to another vulnerability due to the fact that it does not check the extracted file permissions before attempting to delete them. Consequently, an attacker can craft a malicious tar.gz archive in a way that prevents the deletion of its inner files when the manifest generation process is completed. A patch for this vulnerability has been released in versions 2.6.15, 2.7.14, and 2.8.3. Users are advised to upgrade. The only way to completely resolve the issue is to upgrade, however users unable to upgrade should configure RBAC (Role-Based Access Control) and provide access for configuring applications only to a limited number of administrators. These administrators should utilize trusted and verified Helm charts. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2023-40584? 9 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.6.15, 2.7.14, 2.8.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.6.15 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.6.15 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.3 | | `argo-cd` | Bitnami | From 2.4.0 | 2.6.15, 2.7.14, 2.8.3 | | `github.com/argoproj/argo-cd` | Go | All versions | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2023-40584? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.6.15, 2.7.14 or 2.8.3. ## Is CVE-2023-40584 being exploited? There is no known exploitation of CVE-2023-40584 in the wild and no public exploit code. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-40584 and fix it if it is affected. What it is: CVE-2023-40584 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 7 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-40584 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.6.15, 2.7.14, 2.8.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.6.15 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.6.15 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.3 - argo-cd (Bitnami): affected from 2.4.0; fixed in 2.6.15, 2.7.14, 2.8.3 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-40584/ (Markdown: https://insights.sbomify.com/CVE-2023-40584/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40584 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40584 - OSV: https://osv.dev/vulnerability/CVE-2023-40584 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-40584/ Summaries are generated and may contain mistakes; the official description above is the record.