GHSA-gpx9-96j6-pp87

Описание

Summary

This vulnerability allows a user to escape the container network isolation and access the host’s local services (127.0.0.1 bound on the host). The vulnerability is applicable only on the MacOS and Windows environments while using Docker Desktop, Containerd on Lima VM, or Podman.

Details

TaskWeaver is a code-first agent framework for seamlessly planning and executing data analytics tasks. This innovative framework interprets user requests through code snippets and efficiently coordinates a variety of plugins in the form of functions to execute data analytics tasks in a stateful manner. TaskWeaver agents execute code as part of their tasks in a secure manner inside the code interpreter that implements Docker containers under the hood for security reasons. The current Docker client’s configuration can produce insecure outcomes when running on Windows or MacOS host machines while using Docker Desktop, Containerd on Lima, or Podman.

Podman, Containerd, and Docker Desktop, while running on Windows and MacOS, have a “magic domain” inserted by default to each container - allowing direct network access to the host’s localhost from inside the container using the domains “host.docker.internal” (Docker & Podman), “host.containers.internal” (Podman), or “host.lima.internal“ (Containerd on Lima) domains.

PoC

1. Run the following steps on a machine with MacOS or Windows operating system using Docker Desktop or podman.
2. Install TaskWeaver along with its dependencies:

3. Edit the configuration file on which LLM to use (we used Anthropic’s Claude in our tests):

4. Open a new terminal session and activate a simple HTTP server bound to the 127.0.0.1 IP address of the host:

5. For the current PoC we can run the agent in interactive mode (but each use case of the agent is vulnerable):

6. As we use an advanced model, a direct prompt to query “host.docker.internal:1337” would probably seen as malicious and fail, so we will need to trick it using two-steps prompt injection:

7. If all works well you will see a call received on the simple HTTP server from inside the Docker’s container.

Impact

Due to this issue, an attacker can access every local hosted service running on the host, and in cases of unauthenticated sensitive service is found, can also take advantage of them - causing harm to the integrity, availability and confidentiality of information.

Fix suggestion

Initiate the Docker client with the “extra_hosts” parameter running over the magic hostnames rendering them invalid: