GHSA-CV8W-JQG2-JG55
Open redirect via tab character in sign-in redirect
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v0.27.0 | github.com/obot-platform/obot · -11 d desde divulgación | |
| Divulgación | Publicada | GHSA-CV8W-JQG2-JG55 divulgada · CVSS 4.7 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Obot's check on the `rd` redirect parameter could be bypassed by inserting a tab character, such as `/<tab>/evil.example.com`. The check saw a path on Obot's own site, but browsers strip tabs from URLs before following a redirect, so the victim was sent to an external site. An attacker could use a link on the Obot instance's own domain to send users to a phishing page.
Am I affected?
You are affected if you run Obot <= v0.26.3 and either use Obot's built-in local authentication or run with authentication disabled. Deployments that sign users in through an external identity provider do not use this check for sign-in or sign-out. No account is needed to craft the link; a victim has to click it.
Details
Obot accepts a redirect target only if it is a path on the same site, and rejects values beginning with `//` (or `/\`), which browsers treat as a link to another host. The check ran against the raw value and did not account for tab characters, which browsers remove from anywhere in a URL before resolving it. A value like `/<tab>/evil.example.com` passed the check, was written into the redirect response unchanged, and the browser resolved it as `//evil.example.com`. The sign-out endpoint, the redirect after a successful sign-in with Obot's built-in local authentication, and the redirect used when authentication is disabled all returned the value directly as the redirect target.
Impact
An attacker could send a link on the Obot instance's own domain that signs the user out and then sends them to an attacker-controlled site, which is a convincing setup for phishing ("you were signed out, please log in again"). A link to the sign-in page could likewise send the user to an attacker-controlled site immediately after they sign in. This does not expose OAuth authorization codes or tokens: OAuth redirect URIs are validated separately against registered values and are not affected.
Mitigation
Upgrade to v0.27.0 or later, which rejects an `rd` value containing a tab, newline or other control character on these paths and redirects to the Obot home page instead.
Severity
CVSS v3.1 Score: 4.7/10 (Medium) — `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`
Credits
The Obot team would like to thank @Srinivasan-Jayaraman https://github.com/Srinivasan-Jayaraman for responsibly disclosing this issue in accordance with our security policy https://github.com/obot-platform/obot/?tab=security-ov-file.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/obot-platform/obot |
Corregida | v0.27.0 | -11 d | v0.28.1 no afectada |
v0.27.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/obot-platform/obot/security/advisories/GHSA-cv8w-jqg2-jg55Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
