> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/remote-code-execution-via-docker-sock.md).

# Remote code execution via docker.sock

### Synopsis

| Field                | Value                                                                                                                              |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                                            |
| Training Period      | 30 Days                                                                                                                            |
| Test Period          | N/A (single event)                                                                                                                 |
| Deduplication Period | 1 Day                                                                                                                              |
| Required Data        | XDR Agent                                                                                                                          |
| Detector Tags        | Containers                                                                                                                         |
| ATT\&CK Tactic       | Execution (TA0002), Privilege Escalation (TA0004)                                                                                  |
| ATT\&CK Technique    | Container Administration Command (T1609), Command and Scripting Interpreter: Container CLI/API (T1059.013), Escape to Host (T1611) |
| Severity             | Informational                                                                                                                      |

### Description

A process inside a container issued a Docker Engine API request over the docker.sock Unix socket that can lead to remote code execution on another container or the host.

### Attacker's Goals

Execute arbitrary code on another container or the host from inside a container by abusing the Docker Engine API over docker.sock.

### Investigative actions

* Verify whether the process and container legitimately require write access to docker.sock.
* Inspect the container's mounts to confirm docker.sock is exposed.
* Review the full command-line history of the actor process for suspicious activity.

### Variations

<details>

<summary>Remote code execution via docker.sock with a suspicious payload</summary>

**Synopsis**

| Field             | Value                                                                                                                              |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                                                                                  |
| ATT\&CK Technique | Container Administration Command (T1609), Command and Scripting Interpreter: Container CLI/API (T1059.013), Escape to Host (T1611) |
| Severity          | Medium                                                                                                                             |

**Description**

A process inside a container issued a Docker Engine API code-execution request over the docker.sock Unix socket, and the executed command contained suspicious payload.

**Attacker's Goals**

Execute arbitrary code on another container or the host from inside a container by abusing the Docker Engine API over docker.sock.

**Investigative actions**

* Verify whether the process and container legitimately require write access to docker.sock.
* Inspect the container's mounts to confirm docker.sock is exposed.
* Review the full command-line history of the actor process for suspicious activity.

</details>

<details>

<summary>Remote code execution via docker.sock from a first-seen container process</summary>

**Synopsis**

| Field             | Value                                                                                                                              |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                                                                                  |
| ATT\&CK Technique | Container Administration Command (T1609), Command and Scripting Interpreter: Container CLI/API (T1059.013), Escape to Host (T1611) |
| Severity          | Low                                                                                                                                |

**Description**

A process inside a container issued a Docker Engine API code-execution request over the docker.sock Unix socket. This container-image and process pair has not been seen issuing socket commands before in this organization, and the command line itself is not an established one on this host population.

**Attacker's Goals**

Execute arbitrary code on another container or the host from inside a container by abusing the Docker Engine API over docker.sock.

**Investigative actions**

* Verify whether the process and container legitimately require write access to docker.sock.
* Inspect the container's mounts to confirm docker.sock is exposed.
* Review the full command-line history of the actor process for suspicious activity.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/remote-code-execution-via-docker-sock.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
