> 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/pt-br/web/xxe/xxe-file-read-via-external-entities.md).
# Leitura de Arquivo XXE via Entidades Externas
Notas sobre Leitura de Arquivo XXE via Entidades Externas para laboratórios da PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payloads, validação no Burp Suite e contexto de remediação.
### Explorando XXE usando entidades externas para recuperar arquivos
Explore uma vulnerabilidade XXE declarando uma entidade externa para recuperar o conteúdo de um arquivo (aqui `/etc/passwd`) de **Verificar estoque** recurso que faz o parsing de XML e retorna valores inesperados.
O recurso envia XML assim:
{% code overflow="wrap" %}
```xml
2
1
```
{% endcode %}
Se o valor numérico de `` for substituído por uma string, esse valor é refletido na resposta (útil para a operação):
```xml
teste
```
1. Declare uma entidade externa em uma instrução DOCTYPE que aponte para o arquivo do sistema.
```xml
]>
```
2. Chame essa entidade no `` campo retornado pela aplicação.
```
&myFile;
```
3. A resposta deverá então conter o conteúdo do arquivo de destino (`/etc/passwd`).
```xml
]>
&myFile;
1
```
---
# 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/pt-br/web/xxe/xxe-file-read-via-external-entities.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.
