Java Deserialization Scanner
Java Deserialization Scanner is a Burp Suite plugin aimed at detect and exploit Java deserialization vulnerabilities. It was written by Federico Dotta, a Security Expert at @ Mediaservice.net.
The plugin is made up of three different components:
- Integration with Burp Suite active and passive scanner
- Manual tester, for the detection of Java deserialization vulnerabilities on custom insertion points
- Exploiter, that allow to actively exploit Java deserialization vulnerabilies, using frohoff ysoserial (https://github.com/frohoff/ysoserial)
- Federico Dotta, Security Expert at @ Mediaservice.net
Java Deserialization Scanner uses custom payloads generated with a modified version of “ysoserial”, tool created by frohoff and gebl, to detect Java deserialization vulnerabilities. The original tool (https://github.com/frohoff/ysoserial) generate payloads for the execution of commands on the system, using the Runtime.exec function. Usually, however, it is not possible to see the output of the command and consequently it is not simple to write a scanner based on this kind of function. The modified version adds the generation of payloads that execute a syncronous sleep function, very useful to check for the presence of the Java deserialization issues in an automated way.
Currently, the passive checks of the Java Deserialiation Scanner reported the presence of serialized Java objects in the HTTP requests (in raw format or encoded in Base64 or in Ascii Hex) and the active checks actively scan for the presence of weak deserialization functions in conjuction with the presence of the following weak libraries:
- Apache Commons Collections 3 (up to 3.2.1), with three different chains
- Apache Commons Collections 4 (up to 4.4.0), with two different chains
- Spring (up to 4.2.2), with two different chains
- Java 6 and Java 7 (<= Jdk7u21) without any weak library
- Hibernate 5
In the test folder there are some simple Java server applications that can be used to test the plugin. Every application employ a different vulnerable Java library.
The plugin offer a dedicated tab to launch the detection with the sleep payloads on custom insertion points, in order to check the Java deserialization vulnerabilities in particular situations in which strange entry points do not allow the detection with the scanner. The results of the manual tester can be inserted between Burp Suite scanner results.
After that a Java deserialization vulnerability has been found, it is possible to actively exploit the issue with the Exploiting dedicated tab. The plugin allow to configure the path of frohoff ysoserial and use this tool to generate the exploitation payloads. The exploiter, as the other components, supports three different encodings for the payloads: raw, Base64 or Ascii Hex.
- Download Burp Suite: http://portswigger.net/burp/download.html
- Install Java Deserialization Scanner from the BApp Store or follow these steps:
- Download the last release of Java Deserialization Scanner
- Open Burp -> Extender -> Extensions -> Add -> Choose JavaDeserializationScannerXX.jar file
- After installation, the Java Deserialization Scanner active and passive checks will be added to the Burp Suite scanner (it is possible to disable the checks in the options tab)
- Simply run the active or passive scanner in order to check also for weak Java deserialization
- With the dedicated tab “Manual testing” it is possible to set the injection point and executing the attack with all the payloads
- With the dedicated tab “Exploiting” it is possibile to actively exploit Java deserialization vulnerabilites
- The “Configuration” contains all the needed configuration for the correct working of the plugin
In order to improve this extension, please report any issue founded in the plugin. Furthermore if you want report me any disclosed Java library usefull for the exploitation of this weakness and, if I have the time, I will add an active check for it in my plugin.
This software has been created purely for the purposes of academic research and for the development of effective defensive techniques, and is not intended to be used to attack systems except where explicitly authorized. Project maintainers are not responsible or liable for misuse of the software. Use responsibly.