GHSA-2MFP-9VV3-Q737
Command injection in Docker MCP server file setup
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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-2MFP-9VV3-Q737 divulgada · CVSS 6.4 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
On the Docker backend, Obot wrote file-type configuration values for MCP servers into a shell script and ran it in a short-lived init container. Anyone who put a line containing only `EOF` in such a value could end the file early and have the rest of the value run as shell commands in that init container. Supplying these values is an ordinary action for any user who configures an MCP server that has a file-type field.
Am I affected?
You are affected if you run Obot >= v0.9.0, <= v0.26.3 with the Docker backend for MCP server hosting, and either at least one MCP server available to your users has a file-type configuration field, or you have users with the Power User role or higher, who can create such servers themselves. Any authenticated user who can configure such a server can trigger it. Deployments using the Kubernetes backend are not affected.
Details
To place files and configuration into a Docker-hosted MCP server, Obot generated a shell script that wrote each value with a heredoc ending in the delimiter `EOF`, then ran the script in an init container. Values were inserted into the script as-is. Quoting the delimiter prevents variable and command expansion inside the value, but a line consisting only of `EOF` still ends the heredoc, and everything after it runs as shell commands. The script ran when the server was first created and again whenever its file values changed.
Impact
An attacker could run arbitrary commands in the init container that Obot starts to provision that MCP server's files. That container is not privileged and has no Docker socket or host mounts, so the attacker cannot escape it or run commands on the Docker host or in the Obot server. They can modify the MCP server's files volume and reach anything listening on Obot's Docker network, including the Obot server and other MCP server containers.
Mitigation
Upgrade to v0.27.0 or later, which no longer passes file contents through a shell. Obot now copies the files into the init container directly as an archive.
Severity
CVSS v3.1 Score: 6.4/10 (Medium) — `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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-2mfp-9vv3-q737Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
