GHSA-R3M3-5RMH-H3FM
SSRF protection bypasses
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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-R3M3-5RMH-H3FM divulgada · CVSS 4.1 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Obot's outbound request protections, which block remote MCP server URLs and other user-supplied URLs that point at loopback, private or link-local addresses, could be bypassed in three ways. A user able to add a remote MCP server could use the unspecified address `0.0.0.0` (or `::`), or an IPv6 transition address that embeds a blocked IPv4 address, to make Obot send requests to internal destinations. Separately, Obot fetched registry icon URLs with no outbound protections at all.
Am I affected?
You are affected if you run Obot >= v0.14.0, <= v0.26.3 and users with the Power User role or higher can add remote MCP servers or set server icons. Deployments where the administrator already allows loopback, private and link-local destinations for remote MCP servers are not affected, because those destinations were already permitted. The unchecked icon fetch affects releases from v0.14.0 onward. The address bypasses apply from v0.23.0, when the checks they evade were added; earlier releases had no such checks for remote MCP servers.
Details
Obot's outbound checks block requests to loopback, private and link-local addresses, but they did not recognize `0.0.0.0` or `::`, which reach services on the Obot server's own host on most systems. They also did not look inside IPv6 transition addresses (NAT64, 6to4, Teredo and IPv4-compatible addresses), which can carry a blocked IPv4 address. Finally, the registry fetched each server's icon URL to detect its type using a client that had no egress checks.
Impact
An attacker could make Obot send requests to services on the Obot host or its internal network. This is a blind request: for remote MCP servers, Obot sends a fixed MCP initialize request and reports only the response's status code and content type, not its body, unless the destination itself speaks MCP. Icon fetches send a GET request and use the response only to detect an image type. An attacker could learn whether an internal service is reachable but could not read its data.
Mitigation
Upgrade to v0.27.0 or later, which treats `0.0.0.0` and `::` as loopback addresses and checks the IPv4 address embedded in IPv6 transition addresses. Registry icon fetches now apply the same administrator egress settings used for remote MCP servers.
Severity
CVSS v3.1 Score: 4.1/10 (Medium) — `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`
Credits
The Obot team would like to thank @brx-zyy https://github.com/brx-zyy, @tonghuaroot https://github.com/tonghuaroot and @manus-pi https://github.com/manus-pi for responsibly disclosing these issues 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-r3m3-5rmh-h3fmLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
