Skip to content
A Burp extension to detect and exploit versions of Telerik Web UI vulnerable to CVE-2017-9248.
Branch: master
Clone or download
Latest commit e4e9f61 Aug 14, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
images Add files via upload Aug 10, 2018
LICENSE Initial commit Aug 3, 2018
README.md Update README.md Aug 14, 2018
telewreck.py Update telewreck.py Aug 3, 2018

README.md

Telewreck

Version Language License

A Burp extension to detect and exploit versions of Telerik Web UI vulnerable to CVE-2017-9248. This extension is based on the original exploit tool written by Paul Taylor (@bao7uo) which is available at https://github.com/bao7uo/dp_crypto. Credits and big thanks to him.

A related blog post on how to exploit web applications via Telerik Web UI can also be found here.

Features

  • Detect vulnerable versions of Telerik Web UI during passive scans.
  • Bruteforce the key and discover the "Document Manager" link just like the original exploit tool.

Screenshots

Passive Scan

Telewreck Tab

Installation

  1. Download telewreck.py to your machine.
  2. Install Python's requests module using sudo pip install requests.
  3. On your Burp, go to Extender > Options tab. Then under the Python Environment section, locate your jython-standalone-2.7.0.jar file (1) and the directory where Python's requests module is located (2). Burp Tab
  4. Go to Extender > Extensions tab, then click on the Add button. On the new window, browse the location of telewreck.py and click the Next button. Load Telewreck
  5. If there's any error, the Telewreck tab would appear in your Burp. Load Success

Notes

  1. This extension requires Python's requests module. Just run pip install requests to install it.
  2. The text area under Telewreck tab doesn't function as a console. So, stoud and stderr outputs cannot be seen there. However, you can view them under the Output and Errors sections of the Extender tab.
  3. Before running another bruteforce, cancel the current process first by clicking the Cancel button.
  4. If the key can't be bruteforced, then probably the key has been set up securely and/or the application is not using a default installation of Telerik.
  5. If the key can't be bruteforced and/or there are some issues, it's recommended to fall back to the original exploit tool.

To Do

  1. Locate Telerik.Web.UI.DialogHandler.aspx


PS: This is my first time developing a tool so apologies for the poor coding style. Feel free to contribute and improve the development of this tool.

Disclaimer: This tool is created for educational purposes only.

You can’t perform that action at this time.