# CVE-2022-31016: Argo CD vulnerable to Uncontrolled Memory Consumption > An authenticated user can crash the Argo CD repo-server by deploying applications from a repository containing large files, causing a denial of service. - **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:** 25 Jun 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-jhqp-vf4w-rpwq, GO-2022-0495 ## What is CVE-2022-31016? CVE-2022-31016 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 25 Jun 2022. 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. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file. The fix for this vulnerability is available in versions 2.3.5, 2.2.10, 2.1.16, and later. There are no known workarounds. Users are recommended to upgrade. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2022-31016? 12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.1.16, 2.2.10, 2.3.5, 2.4.1 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.1.16 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.1.16 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.2.0 | 2.2.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.2.0 | 2.2.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.3.0 | 2.3.5 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.3.0 | 2.3.5 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.4.1 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.4.1 | | `github.com/argoproj/argo-cd` | Go | From 0.7.0 | None | | `github.com/argoproj/argo-cd` | Go | From 0.7.0 | 2.1.16 | | `github.com/argoproj/argo-cd` | Go | From 0.7.0 | 2.1.16 | Products: Argoproj Argo Cd. ## How do I fix CVE-2022-31016? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.1.16, 2.2.10, 2.3.5 or 2.4.1. ## Is CVE-2022-31016 being exploited? There is no known exploitation of CVE-2022-31016 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-2022-31016 and fix it if it is affected. What it is: CVE-2022-31016 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 25 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-31016 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16, 2.2.10, 2.3.5, 2.4.1 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.2.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.2.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.3.0; fixed in 2.3.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.3.0; fixed in 2.3.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.4.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.4.1 - github.com/argoproj/argo-cd (Go): affected from 0.7.0; no fix listed - github.com/argoproj/argo-cd (Go): affected from 0.7.0; fixed in 2.1.16 - github.com/argoproj/argo-cd (Go): affected from 0.7.0; fixed in 2.1.16 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-2022-31016/ (Markdown: https://insights.sbomify.com/CVE-2022-31016/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31016 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31016 - OSV: https://osv.dev/vulnerability/CVE-2022-31016 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-31016/ Summaries are generated and may contain mistakes; the official description above is the record.