cve.bz

CVE-2024-22424 Cross Site Reference Forgery

8.3 highExploit referenceEPSS 0.5%Fix available

High (8.3). EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-cd/v2 2.10-rc2, 2.7.16, 2.8.8.

On this page
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.

Severity

CVSS 3.1

8.3 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-22424 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-22424?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-22424?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-22424 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
argoproj:argo_cdfrom 2.8.0 before 2.8.8
argoproj:argo_cdfrom 2.9.0 before 2.9.4
argoproj:argo_cd2.10.0:rc1
linuxfoundation:argo-cdfrom 0.1.0 before 2.7.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-92mw-q256-5vwgGogithub.com/argoproj/argo-cd>=0.1.0 <=1.8.7no fix published
GHSA-92mw-q256-5vwgGogithub.com/argoproj/argo-cd/v2<2.7.162.7.16
GHSA-92mw-q256-5vwgGogithub.com/argoproj/argo-cd/v2>=2.8.0-rc1 <2.8.82.8.8
GHSA-92mw-q256-5vwgGogithub.com/argoproj/argo-cd/v2>=2.9.0-rc1 <2.9.42.9.4
GHSA-92mw-q256-5vwgGogithub.com/argoproj/argo-cd/v2>=2.10.0-rc1 <2.10-rc22.10-rc2

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat OpenShift GitOps 1.10openshift-gitops-1/argocd-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/argo-rollouts-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/console-plugin-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/dex-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/gitops-operator-bundle:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/gitops-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/gitops-rhel8-operator:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/kam-delivery-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.10openshift-gitops-1/must-gather-rhel8:v1.10.2-2Fixed 2024-02-05RHSA-2024:0692
Red Hat OpenShift GitOps 1.11openshift-gitops-1/argocd-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/argo-rollouts-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/console-plugin-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/dex-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/gitops-operator-bundle:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/gitops-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/gitops-rhel8-operator:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/kam-delivery-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.11openshift-gitops-1/must-gather-rhel8:v1.11.1-1Fixed 2024-02-05RHSA-2024:0689
Red Hat OpenShift GitOps 1.9openshift-gitops-1/argocd-rhel8:v1.9.4-1Fixed 2024-02-05RHSA-2024:0691
Red Hat OpenShift GitOps 1.9openshift-gitops-1/argo-rollouts-rhel8:v1.9.4-1Fixed 2024-02-05RHSA-2024:0691
7 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-22424.

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON