Описание
Docker MCP Plugin and Docker MCP Gateway have DNS Rebinding vulnerability when running in sse or streaming mode
Impact
When ran in sse or streaming mode (--transport), the Docker MCP Gateway is vulnerable to a DNS rebinding attack.
Vulnerability allows for Browser-Based exploitation of any MCP servers that are executing within the Docker MCP Gateway. Any tools or other features exposed by MCP servers can be manipulated by an attacker who is able to get a victim to visit a malicious website, or if a victim is served a malicious advertisement.
The MCP Gateway is not prone to this attack when started in its default stdio mode, which does not listen on any network ports.
Patches
Patch available in version v0.28.0
Workarounds
Do not start the MCP gateway in sse or streaming mode (use default stdio)
Ссылки
- https://github.com/docker/mcp-gateway/security/advisories/GHSA-46gc-mwh4-cc5r
- https://nvd.nist.gov/vuln/detail/CVE-2025-64443
- https://github.com/docker/mcp-gateway/pull/190
- https://github.com/docker/mcp-gateway/commit/6b076b2479d8d1345c50c112119c62978d46858e
- https://github.com/docker/mcp-gateway/commit/fe073985c8eb6e0c9317d2f198c07686f70ea06d
- https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#security-warning
Пакеты
github.com/docker/mcp-gateway
<= 0.27.0
0.28.0
Связанные уязвимости
MCP Gateway allows easy and secure running and deployment of MCP servers. In versions 0.27.0 and earlier, when MCP Gateway runs in sse or streaming transport mode, it is vulnerable to DNS rebinding. An attacker who can get a victim to visit a malicious website or be served a malicious advertisement can perform browser-based exploitation of MCP servers executing behind the gateway, including manipulating tools or other features exposed by those MCP servers. MCP Gateway is not affected when running in the default stdio mode, which does not listen on network ports. Version 0.28.0 fixes this issue.