> 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/adm-group-linux-privilege-escalation.md).
# adm 组日志访问 - Linux 权限提升
用户组（adm）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
危险的本地组成员资格可能无需内核漏洞利用即可暴露特权资源。docker、lxd、adm 或 proxy 等组可能授予主机控制权、敏感日志访问权限，或可用于横向移动和提权到 root 的配置路径。本页具体聚焦于 **用户组（adm）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
id
groups
```
## 示例
> adm 组通常具有访问 /var/log 目录中的系统日志以及其他与系统管理相关资源的权限。
通过 **查找** 我们搜索所有服务器日志：
```bash
find /var/log -group adm 2>/dev/null
```
我们发现我们可以访问日志，例如来自 **apache2**:
这些文件通常包含 **敏感信息**:
---
# 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/user-groups/adm-group-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.
