# CVE-2024-22424: Cross-Site Request Forgery (CSRF) in github.com/argoproj/argo-cd > Attackers can perform CSRF attacks on Argo CD by bypassing CORS checks via content type manipulation, potentially executing malicious code. - **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Jan 2024 - **Updated:** 30 May 2025 - **Also known as:** GHSA-92mw-q256-5vwg ## What is CVE-2024-22424? CVE-2024-22424 is a high-severity vulnerability in Argoproj Argo Cd, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD. A CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code. Argo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request. Many companies host Argo CD on an internal subdomain. If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API. Browsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request. Before the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code). A patch for this vulnerability has been released in the following Argo CD versions: 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15. The patch contains a breaking API change. The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2024-22424? 10 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.7.16 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.7.16 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0-rc1 | 2.10-rc2 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0-rc1 | 2.10-rc2 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0-rc1 | 2.8.8 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0-rc1 | 2.8.8 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.9.4 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.9.4 | | `github.com/argoproj/argo-cd` | Go | From 0.1.0 to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | From 0.1.0 to 1.8.7 | None | Products: Argoproj Argo Cd, Linuxfoundation Argo-Cd. ## How do I fix CVE-2024-22424? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.7.16, 2.10-rc2, 2.8.8 or 2.9.4. ## Is CVE-2024-22424 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22424 exists. ## 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-22424 and fix it if it is affected. What it is: CVE-2024-22424 is a high-severity vulnerability in Argoproj Argo Cd, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22424 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.7.16 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.7.16 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0-rc1; fixed in 2.10-rc2 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0-rc1; fixed in 2.10-rc2 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0-rc1; fixed in 2.8.8 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0-rc1; fixed in 2.8.8 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.9.4 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.9.4 - github.com/argoproj/argo-cd (Go): affected from 0.1.0 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd (Go): affected from 0.1.0 up to 1.8.7; 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-22424/ (Markdown: https://insights.sbomify.com/CVE-2024-22424/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22424 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22424 - OSV: https://osv.dev/vulnerability/CVE-2024-22424 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-22424/ Summaries are generated and may contain mistakes; the official description above is the record.