Burp Suite extension to track vulnerability assessment progress.
- Capture items (unique requests) from the Burp Suite tools (Proxy, Repeater, Target). Request unique key is defined as follows: target (host, port, protocol), path and method.
- Items have following editable properties:
- status (Blocked, Done, Ignored, In progress, New, Postponed)
- Items can be filtered by:
- tags (there are two filtering modes: AND – item has to have all filtering tags OR – item has to have at least one of the filtering tags)
- Exclude requests from capture based on the path extension or response status code
- Selected items can be sent to the Burp Suite tools: Intruder, Repeater or Scanner
- Selected item is displayed in the full functional Burp Suite HTTP message editor
- Path patterns – unique key of the request is defined by target, path and method. However it can be usefull to define path pattern (regexp) to consider different requests as the same item (e.g. /article/d+?/comments path pattern groups following requests: /article/1/comments, /article/2/comments, /article/100/comments, etc.)
- Optionally, items and path patterns can be persisted to keep the state between Burp Suite runnings (please see Requirements)
- Database – selects file to persist items and path patterns (please see Requirements)
- Scope tools – enables items capturing for selected Burp Suite tools (Proxy, Repeater, Target)
- Excluded extensions – requests with these path extensions won’t be processed
- Excluded status codes – responses (and related requests) with these status codes won’t be processed
- Overwrite duplicate items – the current item will be replaced by the newest duplicate (state of the item is preserved)
- Process only in-scope requests
- Set In progress status when sending item to tool
To persist items and path patterns SQLite JDBC driver is required.
- Download driver from https://mvnrepository.com/artifact/org.xerial/sqlite-jdbc
- Put downloaded driver (jar file) in the folder on the disk (e.g. /home/user/burpsuite-jars)
- Set Burp Suite option (Extender -> Options -> Java Environment) to the path of folder with the driver
- Reload the extension
Please see the CHANGELOG