> 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/permissions/etc-passwd-write-abuse-linux-privilege-escalation.md).
# /etc/passwd 写入滥用 - Linux 权限提升
权限管理（/etc/passwd）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
基于权限的提权会利用可写文件、薄弱的所有权、暴露的机密信息，或本应仅由 root 控制的敏感路径。小小的权限错误一旦影响到认证文件或特权执行路径，就可能直接获得 root 访问权限。本页重点关注 **权限管理（/etc/passwd）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
find / -writable 2>/dev/null
ls -la /etc/passwd /etc/shadow 2>/dev/null
```
## 示例
如果我们按系统的\*\*可写性\*\*筛选文件，那么 /etc/passwd
```bash
find / -writable 2>/dev/null
```
我们将这个字符串粘贴到 root 用户上，系统会先从 /etc/passwd 而不是 /etc/shadow 中读取它：
---
# 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/permissions/etc-passwd-write-abuse-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.
