In Apache Batik before 1.9, files lying on the filesystem of the server which uses batik can be revealed to arbitrary users who send maliciously formed SVG files. The file types that can be shown depend on the user context in which the exploitable application is running. If the user is root a full compromise of the server - including confidential or sensitive files - would be possible. XXE can also be used to attack the availability of the server via denial of service as the references within a xml document can trivially trigger an amplification attack.
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Batik | Apache | * | 1.8 (including) |
| Red Hat JBoss A-MQ 6.3 | RedHat | switchyard | * |
| Red Hat JBoss BPMS 6.4 | RedHat | batik | * |
| Red Hat JBoss BRMS 6.4 | RedHat | batik | * |
| Red Hat JBoss Fuse 6.3 | RedHat | switchyard | * |
| Batik | Ubuntu | artful | * |
| Batik | Ubuntu | esm-apps/xenial | * |
| Batik | Ubuntu | precise | * |
| Batik | Ubuntu | trusty | * |
| Batik | Ubuntu | upstream | * |
| Batik | Ubuntu | xenial | * |
| Batik | Ubuntu | yakkety | * |
| Batik | Ubuntu | zesty | * |
XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing. By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as “file:///c:/winnt/win.ini” designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents.