llamaCVEVulnerability Intelligence
/
argo-cd

CVE-2024-22424

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

Sin parche publicadocross-site request forgery (CSRF)
Descargar PNG JSON
CVSS 3.1
8.4
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H Fuente: CNA
ExplotaciónPoC públicaSSVC: poc · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición1.035 dDesde la divulgación, 18 ene 2024, 7:25 p. m.
Detección1.033 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Existe PoC pública, no automatizable e impacto técnico total. No hay versión corregida: aplique mitigaciones.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC
Modificada
Explotación
Remediación
Parche v2.9.4 +1
Parche v2.7.16 +1
Monitoreo
Detectada
18 ene 24
19 ene 24
8 may 25
30 may 25
17 nov 26
19 nov 26
18 ene 24
3 oct 24
19 jun 25
5 mar 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche v2.9.4 github.com/argoproj/argo-cd/v2 · -1 d desde divulgación
Remediación Parche v2.10.0-rc2 github.com/argoproj/argo-cd/v2 · -1 d desde divulgación
Divulgación Publicada CVE-2024-22424 divulgada · CVSS 8.4 (CNA)
Remediación Parche v2.7.16 github.com/argoproj/argo-cd/v2 · 0 d desde divulgación
Remediación Parche v2.8.8 github.com/argoproj/argo-cd/v2 · 0 d desde divulgación
Divulgación Evaluación SSVC CISA-ADP · explotación PoC pública
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen

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.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
github.com/argoproj/argo-cd/v2< 2.7.16
github.com/argoproj/argo-cd≥ 0.1.0 ≤ 1.8.7
argo-cd≥ 0.1.0 < 2.7.15
github.com/argoproj/argo-cd/v2≥ 2.8.0-rc1 < 2.8.8
argo-cd≥ 2.8.0 < 2.8.8
github.com/argoproj/argo-cd/v2≥ 2.9.0-rc1 < 2.9.4
argo-cd≥ 2.9.0 < 2.9.4
argo-cd · github.com/argoproj/argo-cd/v2≥ 2.10.0-rc1 < 2.10-rc2
0.1.0
v1.8.7
2.7.15
2.7.16
2.8.0
2.8.8
2.9.0-rc1
2.9.4
2.10-rc2
2.10.0-rc1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/argoproj/argo-cd
Sin parche — — v1.8.7 afectada
gogithub.com/argoproj/argo-cd/v2
Corregida v2.7.16, v2.8.8, v2.9.4, v2.10.0-rc2 0 d · 0 d · -1 d · -1 d v2.14.21 no afectada
Versiones corregidas2.7.15v2.7.162.8.8v2.8.82.9.4v2.9.42.10-rc2v2.10.0-rc2
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/argoproj/argo-cd/security/advisories/GHSA-92mw-q256-5vwg
Otrahttps://github.com/argoproj/argo-cd/issues/2496
Otrahttps://github.com/argoproj/argo-cd/pull/16860

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.