MCP Gateway: Argument injection via OCI image label YAML in Docker MCP Gateway
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 8.7epss 0.2%
probabilidade de exploração
0.2%top 90% das CVEs
exploração observada
nãonenhuma fonte reporta
MCP Gateway allows easy and secure running and deployment of MCP servers. From 0.21.0 until 0.42.2, Docker MCP Gateway YAML-unmarshalled the attacker-controlled io.docker.server.metadata OCI image label into the broad catalog.Server structure for direct docker:// references and catalog snapshot imports in pkg/oci/self_contained.go and pkg/workingset/workingset.go. Runtime-shaping fields including Volumes, User, and ExtraHosts were then appended to the docker run argument vector without an origin allowlist, allowing a malicious image author to request host filesystem or Docker socket mounts and UID 0 execution when a victim selected or pulled the image. This container-creation-time boundary bypass can execute arbitrary code on the host and is not prevented by no-new-privileges because no in-container privilege escalation is required. This issue is fixed in version 0.42.2.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Produtos afetados
docker · mcp-gatewayReferências
https://github.com/docker/mcp-gateway/commit/306d2d94a3b526f43281313321bf784f2d46a7fehttps://github.com/docker/mcp-gateway/commit/439b2200d9e26a4ff414aeb043785df45a78422bhttps://github.com/docker/mcp-gateway/pull/498https://github.com/docker/mcp-gateway/releases/tag/v0.42.2https://github.com/docker/mcp-gateway/security/advisories/GHSA-r2xf-7jw5-pjg6