llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/obot-platform/obot

GHSA-JWGP-HQMV-M4P6

Cross-site request forgery from same-site origins lets an attacker act as a signed-in Obot user

Sin parche publicado
Descargar PNG JSON
CVSS 3.1
7.1
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición23 hDesde la divulgación, 20 nov 2026, 10:18 a. m.
Detección53 minDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir de cerca
Monitorear y programar la remediación
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico total. No hay versión corregida: aplique mitigaciones.
Que no se te pase entre tantos tickets.Esto huele a PoC esperando su momento.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
10:18 a. m.
11:11 a. m.
09:03 a. m.
10:18 a. m.
03:59 p. m.
09:41 p. m.
03:22 a. m.
09:03 a. m.
FechaFaseEventoDetalle
Divulgación Publicada GHSA-JWGP-HQMV-M4P6 divulgada · CVSS 7.1 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

Obot accepted state-changing API requests authenticated only by the browser's session or bootstrap cookie without checking where the request came from. An attacker who can run script on another origin under the same parent domain as an Obot deployment could get a signed-in user's browser to send requests that Obot performs with that user's role, including Owner and Admin. For example, the attacker could create a local account with a password they know and then sign in as an administrator.

Am I affected?

All Obot releases `<= v0.28.1` are affected if an attacker can serve script from an origin on the same site as your Obot deployment, such as another subdomain of the same parent domain (for example, `b.example.com` targeting `a.example.com`). This includes other Obot deployments under that domain whose administrators you do not trust. A signed-in user, or a browser still holding the setup bootstrap cookie, must also open attacker-controlled content. Deployments whose parent domain hosts no origins that untrusted parties can serve script from are not affected.

Details

Browsers attach `SameSite=Lax` cookies to requests between origins on the same site, so the session cookie did not protect against requests from sibling subdomains, and the bootstrap cookie set no `SameSite` attribute at all. Obot's API also parsed request bodies as JSON regardless of their declared content type, so a `text/plain` POST, which browsers send without a CORS preflight, reached handlers as a valid request. Only POST requests are exploitable: other methods and custom headers trigger a preflight, and Obot's CORS policy never allows credentials. The attacker cannot read responses, but the actions take effect.

Impact

An attacker could perform any POST action the victim is authorized for, with the victim's role. Against an Owner or Admin, this includes creating local accounts with attacker-known credentials (when the local auth provider is enabled), adding MCP servers that run attacker-controlled images or point to attacker URLs, redirecting model providers to an attacker-controlled endpoint to capture prompts and responses, and changing access rules and other configuration. A browser holding an unexpired bootstrap cookie gives the attacker Owner-level actions. API keys and bearer tokens are not affected, because a cross-origin page cannot attach them to requests.

Mitigation

Upgrade to v0.28.2 or later. The fixed release rejects state-changing requests authenticated only by the session or bootstrap cookie unless they come from Obot's own server or UI origins. It applies the same check to local logins, requires a cookie set during the setup sign-in flow before completing it, and refuses sign-outs started by another site. The bootstrap cookie is now `SameSite=Lax`, and the setup cookie uses the `__Host-` prefix over HTTPS so a sibling subdomain cannot set it.

Severity

CVSS v3.1 Score: 7.1/10 (High) — `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L`

Credits

The Obot team would like to thank @ivyjeong13 https://github.com/ivyjeong13 for responsibly disclosing this issue in accordance with our security policy https://github.com/obot-platform/obot/?tab=security-ov-file.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:L
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
5.9/ 10Medio
Vector 5.9 (moderada) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/obot-platform/obot≤ 0.28.1
0.28.1
v0.28.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/obot-platform/obot
Sin parche — — v0.28.1 afectada
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/obot-platform/obot/security/advisories/GHSA-jwgp-hqmv-m4p6

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