CVE-2024-22424 Cross-Site Request Forgery (CSRF) in github.com/argoproj/argo-cd

High 8.4 Published Updated

Attackers can perform CSRF attacks on Argo CD by bypassing CORS checks via content type manipulation, potentially executing malicious code.

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

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

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.

PackageAffectedFixed in
github.com/argoproj/argo-cd/v2 GoAll versions2.7.16
github.com/argoproj/argo-cd/v2 GoAll versions2.7.16
github.com/argoproj/argo-cd/v2 GoFrom 2.10.0-rc12.10-rc2
github.com/argoproj/argo-cd/v2 GoFrom 2.10.0-rc12.10-rc2
github.com/argoproj/argo-cd/v2 GoFrom 2.8.0-rc12.8.8
github.com/argoproj/argo-cd/v2 GoFrom 2.8.0-rc12.8.8
4 more packages
github.com/argoproj/argo-cd/v2 GoFrom 2.9.0-rc12.9.4
github.com/argoproj/argo-cd/v2 GoFrom 2.9.0-rc12.9.4
github.com/argoproj/argo-cd GoFrom 0.1.0 to 1.8.7None
github.com/argoproj/argo-cd GoFrom 0.1.0 to 1.8.7None

Products include 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.

All Argoproj Argo Cd vulnerabilities

Sources

Also known as GHSA-92mw-q256-5vwg.

Is CVE-2024-22424 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free