目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1336

100%

CVE-2025-54253 PoC — Adobe Experience Manager 安全漏洞

来源
关联漏洞
标题: Adobe Experience Manager 安全漏洞 (CVE-2025-54253)
Description:Adobe Experience Manager(AEM)是美国奥多比(Adobe)公司的一套可用于构建网站、移动应用程序和表单的内容管理解决方案。该方案支持移动内容管理、营销销售活动管理和多站点管理等。 Adobe Experience Manager(AEM)6.5.23及之前版本存在安全漏洞,该漏洞源于配置不当,可能导致任意代码执行。
Description
Simulated PoC for CVE-2025-54253: Adobe AEM OGNL Injection Vulnerability
介绍
![CVE](https://img.shields.io/badge/CVE-2025--54253-red)
![Exploit-Status](https://img.shields.io/badge/status-exploitable-critical)
![Python](https://img.shields.io/badge/Python-3.10%2B-blue)
![License](https://img.shields.io/badge/License-MIT-green)
![PoC](https://img.shields.io/badge/PoC-Verified-brightgreen)

# 🚨 CVE-2025-54253 – Adobe AEM Forms on JEE OGNL Injection to RCE

## 🔎 Overview

**CVE-2025-54253** is a critical OGNL injection vulnerability in **Adobe AEM Forms on JEE**. It allows unauthenticated attackers to execute arbitrary operating system commands via the `/adminui/debug?debug=OGNL:` endpoint.

- **Severity:** Critical
- **CVSS Score:** 9.8 (Pending)
- **Attack Vector:** Remote
- **Authentication Required:** No
- **Affected Product:** Adobe AEM Forms on JEE (<= 6.5.23.0)
- **Status:** Confirmed exploitability

---

## 🧠 Technical Details

This vulnerability lies in an exposed debugging interface that evaluates user-controlled OGNL expressions without proper sanitization or authentication. Exploiting it can lead to remote code execution under the context of the application server.

> 📝 **Note:** This vulnerability affects installations that expose `/adminui/debug` endpoint publicly or internally without proper access control.

---

## 🧪 Proof of Concept (PoC)

### 🔸 HTTP Payload Vector

Simple OGNL expressions demonstrate command execution via browser or curl.

```bash
curl "http://localhost:4502/adminui/debug?debug=OGNL:whoami"
```

### 📄 PoC Script

[`cve-2025-54253-poc.py`](./poc/cve-2025-54253-poc.py)

```bash
python3 poc/cve-2025-54253-poc.py --url http://127.0.0.1:4502 --cmd "whoami"
```

### 🧾 Sample Exploit Log

The script logs command execution output to `exploit.log`:

[`exploit.log`](./logs/exploit.log)

---

## 🛠️ Steps to Reproduce

1. Set up a vulnerable Adobe AEM instance (<= 6.5.23.0).
2. Start Flask server (if simulating locally):  
   ![Flask Running](screenshots/1_flask_server_running.png)

3. Execute OGNL in browser:  
   ![Browser Execution](screenshots/2_browser_OGNL_whoami_execution.png)

4. Execute via curl:  
   ![Curl Execution](screenshots/3_curl_OGNL_whoami_execution.png)

5. Output from commands:  
   ![id](screenshots/4_OGNL_id_command_output.png)  
   ![uname -a](screenshots/5_OGNL_uname-a_command_output.png)  
   ![ls -la](screenshots/6_OGNL_ls-la_directory_listing.png)

6. Flask logging view:  
   ![Flask Logs](screenshots/7_flask_server_logs.png)

7. PoC script run:  
   ![Script Execution](screenshots/8_poc_script_execution.png)

8. Verbose log view:  
   ![Log Output](screenshots/9_exploit_log_verbose.png)

---

## 🧰 Tools & Technologies Used

- Python (PoC scripting)
- Flask (simulated server)
- Kali Linux
- curl & browser
- GitHub (PoC publishing)

---

## ✅ Mitigation

- Restrict access to `/adminui/debug`
- Apply vendor patches as available
- Monitor for unauthorized OGNL expressions in access logs
- Use WAF or proxy filtering to block such patterns

---

> ⚠️ **Disclaimer:**  
> This PoC is for educational purposes only. Do **not** use it against systems you do not own or have explicit permission to test.

---

## 👨‍💻 Author

**Shivshant Patil**  
Certified Ethical Hacker (CEH v13)  
B.Tech Computer Engineering Graduate  
🔗 [LinkedIn](https://www.linkedin.com/in/shivshant-patil-b58aaa281)  
🔗 [GitHub](https://github.com/Shivshantp)

---

## 📚 References

- 🔗 [Adobe Security Advisory (placeholder)](https://helpx.adobe.com/security.html)
- 🔗 [NVD Entry - CVE-2025-54253](https://nvd.nist.gov/vuln/detail/CVE-2025-54253)
- 🔗 [Exploit Database](https://www.exploit-db.com)
文件快照

登录后查看神龙缓存的 POC 文件快照

登录查看
备注
    1. 建议优先通过来源进行访问。
    2. 本地 POC 快照面向订阅用户开放;当原始来源失效或无法访问时,本地镜像作为订阅权益的一部分提供。
    3. 持续抓取、验证、维护这份 POC 档案需要不少投入,因此本地快照已纳入付费订阅。您的订阅是让这份资料能继续走下去的关键,由衷感谢。 查看订阅方案 →