# CVE-2024-32476: Denial of Service via malicious jqPathExpressions in ignoreDifferences

> Attackers can cause a Denial of Service via Out-of-Memory errors in Argo CD by submitting malicious jqPathExpressions in ignoreDifferences configurations.

- **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:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-argo-cd-2024-32476, GHSA-9m6p-x4h2-6frq, GO-2024-2792

## What is CVE-2024-32476?

CVE-2024-32476 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 26 Apr 2024. 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. There is a Denial of Service (DoS) vulnerability via OOM using jq in ignoreDifferences. This vulnerability has been patched in version(s) 2.10.7, 2.9.12 and 2.8.16.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-32476?

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 | All versions | 2.8.17, 2.9.13, 2.10.8 |
| `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.8.17 |
| `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.8.17 |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.8 |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.8 |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.13 |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.13 |
| `argo-cd` | Bitnami | All versions | 2.9.13, 2.10.8 |
| `github.com/argoproj/argo-cd` | Go | All versions | None |

Products: Argoproj Argo Cd.

## How do I fix CVE-2024-32476?

Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.8.17, 2.9.13 or 2.10.8.

## Is CVE-2024-32476 being exploited?

There is no known exploitation of CVE-2024-32476 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-2024-32476 and fix it if it is affected.

What it is: CVE-2024-32476 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 26 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32476 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.8.17, 2.9.13, 2.10.8
- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.8.17
- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.8.17
- github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.8
- github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.8
- github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.13
- github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.13
- argo-cd (Bitnami): affected all versions; fixed in 2.9.13, 2.10.8
- 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-2024-32476/ (Markdown: https://insights.sbomify.com/CVE-2024-32476/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32476
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32476
- OSV: https://osv.dev/vulnerability/CVE-2024-32476

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32476/
Summaries are generated and may contain mistakes; the official description above is the record.