HP Security Research Threat Intelligence Briefing - Episode 6

"Wait, I'm not clear on what's happening here. Is this even possible? Just by giving an application a single piece of XML, you can cause it to steal other files for you?"

 

Those were a customer’s words when an XML External Entity injection vulnerability was reported on his system. XML is a simple, logical way to represent data and many developers are unaware of the flaws they could be introducing. In this podcast episode, we review some of the risks associated with processing user-supplied XML documents and learn about countermeasures for mitigating them.

 

The following topics will be covered:

  • XML External Entity Injection (XXE)
  • XML Entity Expansion Injection (XEE)
  • Server-Side Request Forgery Attacks (SSRF)
  • Case Study: Attacking RESTful APIs

 

The threats presented in this podcast have been well known since the early 2000s, but even popular frameworks like Spring MVC are still vulnerable to XXE among other technologies. By sharing this analysis, we hope to emphasize how important it is to process XML documents securely in your organization.

 

Modern web applications make extensive use of XML documents. These documents are used to store, transform and transmit data. If your company is exposing a public RESTful API that consumes XML messages - perhaps as a backend service for your organization’s mobile apps - then chances are high that your organization is vulnerable to these types of attack. 

To learn more on this interesting topic listen to Episode 6 of the HP Threat Intelligence Briefing Podcast, available on the Web and iTunes, and read the companion report for more details.

Until the next time we meet, be vigilant and stay secure.

 

Labels: threatbriefings
Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.