> 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/permissions/etc-passwd-write-abuse-linux-privilege-escalation.md).
# /etc/passwd Write Abuse - Linux Privilege Escalation
Permission Management (/etc/passwd) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.
## What It Is
Permission-based privilege escalation abuses writable files, weak ownership, exposed secrets, or sensitive paths that should only be controlled by root. Small permission mistakes can become direct root access when they affect authentication files or privileged execution paths. This specific page focuses on **Permission Management (/etc/passwd)** and keeps the exploitation flow practical: identify the condition, validate it safely, then run the smallest payload needed to prove impact.
## Enumeration
Start by confirming the local context and the exact misconfiguration before running the exploit path.
```bash
find / -writable 2>/dev/null
ls -la /etc/passwd /etc/shadow 2>/dev/null
```
## Examples
If we filter the files with the \*\* writeability\*\* of the system, then the /etc/passwd
```bash
find / -writable 2>/dev/null
```
With **openssl**, if we create a password, it returns it to SSL format
```bash
openssl passwd
```
We paste this string on the root user and the system will read it from /etc/passwd before /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/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.
