XML External Entity (XXE) Injection Affecting org.apache.activemq:activemq-core Open this link in a new tab package, versions [0,]
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.Test your applications
19 Oct 2015
19 Oct 2015
How to fix?
There is no fixed version for
org.apache.activemq:activemq-core is a core package for ActiveMQ Message Broker and Client implementations.
Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. This could allow remote consumers to have unspecified impact via vectors involving an XPath based selector when dequeuing XML messages.
XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.
Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.
For example, below is a sample XML document, containing an XML element- username.
<xml> <?xml version="1.0" encoding="ISO-8859-1"?> <username>John</username> </xml>
An external XML entity -
xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of
/etc/passwd and display it to the user rendered by
<xml> <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "file:///etc/passwd" >]> <username>&xxe;</username> </xml>
Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.