> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/privesc/docker-escape.md).

# Docker Escape

Docker escape privilege escalation notes for default Docker Toolbox credentials, SUID manipulation, password reuse, and SSH key pivoting.

Docker escape paths abuse container misconfiguration, mounted host resources, default credentials, reused passwords, or excessive container privileges. The objective is to move from the container context to host-level access.

## Methodology

* Identify whether the shell is inside a container and inspect mounts, capabilities, and exposed sockets.
* Check for mounted host paths, SSH keys, reused credentials, and writable SUID binaries.
* Use the least intrusive escape path that proves host access.

## Quick Checks

```bash
id
cat /proc/1/cgroup
mount
ls -la /var/run/docker.sock 2>/dev/null
```

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-docker" style="color:$primary;">:docker:</i></h3></td><td><h4>Docker Password Reuse</h4></td><td>Docker Escape (Password Reuse) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/docker-escape/docker-password-reuse-linux-privilege-escalation.md">Docker Password Reuse - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-docker" style="color:$primary;">:docker:</i></h3></td><td><h4>Docker SUID Permission Manipulation</h4></td><td>Docker Escape (SUID Permission Manipulation) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/docker-escape/docker-suid-permission-manipulation-linux-privilege-escalation.md">Docker SUID Permission Manipulation - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-docker" style="color:$primary;">:docker:</i></h3></td><td><h4>Docker Escape with SSH Keys</h4></td><td>Docker Escape (SSH Keys) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/docker-escape/docker-ssh-keys-linux-privilege-escalation.md">Docker Escape (SSH Keys) - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-docker" style="color:$primary;">:docker:</i></h3></td><td><h4>Docker Toolbox Default Credentials</h4></td><td>Docker Escape (Docker Toolbox Default Credentials) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/docker-escape/docker-toolbox-default-credentials-linux-privilege-escalation.md">Docker Escape (Docker Toolbox Default Credentials) - Linux Privilege Escalation</a></td></tr></tbody></table>


---

# 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://hacking-notes.jord4n.pro/privesc/docker-escape.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.
