GHSA-4H4X-WCCP-CRRX
Open redirect in the Obot UI's trailing-slash handling
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 |
|---|---|---|---|
| Divulgación | Publicada | GHSA-4H4X-WCCP-CRRX divulgada · CVSS 4.7 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The Obot UI redirects any path that ends in a slash to the same path without it, but did not check what the remaining path was. A crafted link such as `https://obot.example.com/%2Fevil.example/` made Obot redirect the browser to `evil.example`. An attacker could use links that start with a trusted Obot URL to send users to a page that imitates the Obot sign-in or an OAuth consent screen.
Am I affected?
Obot releases `>= v0.15.0, <= v0.28.1` are affected. No account or configuration is needed to exploit it: the attacker only needs a victim to open a crafted link to your Obot host.
Details
The UI redirected paths with a trailing slash to their decoded form with the slash removed. Because the path was decoded, an encoded slash (`%2F`) at the start of the path produced a redirect target beginning with `//`, which browsers treat as a link to a different host. An encoded backslash (`%5C`) or tab (`%09`) had the same effect, because browsers treat a backslash as a slash and ignore tabs in URLs. This is the same class of issue as GHSA-v8vw-gw5j-w7m6 and GHSA-cv8w-jqg2-jg55, in a different part of Obot.
Impact
An attacker could make a link on your Obot host redirect a user to an attacker-controlled site, for use in phishing. The redirect alone does not expose any Obot data, sessions, or credentials, and it does not let the attacker act as the user in Obot.
Mitigation
Upgrade to v0.28.2 or later. The fixed release collapses leading slashes in the redirect target and escapes it, so a trailing-slash redirect always stays on the Obot host.
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 @amanverma-wsu https://github.com/amanverma-wsu, @swarnpriya https://github.com/swarnpriya, @gaopeng32 https://github.com/gaopeng32, and @basavesh https://github.com/basavesh 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.
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 |
Sin parche | — | — | v0.28.1 afectada |
Arsenal 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-4h4x-wccp-crrxLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
