Compatible with Burp Suite Enterprise Edition
Please note that extensions are written by third-party users of Burp, and PortSwigger makes no warranty about their quality or usefulness for any particular purpose.
- Customise the header name using the
HEADER_NAME
variable if required. The default name isUuid
. - Build the extension
- Add the extension to the Burp Suite Enterprise Edition extension library, and add the extension to your required Site.
- Configure your session handling rule in Burp Suite Professional to invoke the extension, using the required extension action handler and scope. An example session handling rule for the "Custom Header Action - Random UUID Value" action has been included for reference.
- Import the session handling rule as a scan configuration into Burp Suite Enterprise Edition and add the scan configuration to your required site.
- Load the extension into
Extensions > Installed > Add
- Go to
Settings > Search > Sessions
- Under
Session handling rules
, go toAdd > Rule actions > Add > Invoke a Burp extension
, select the requiredCustom Header Action
option from the extension action handler dropdown list and clickOK
- Set your Rule description
- Click across to the
Scope
tab, ensuring that theTools scope > Scanner
box is checked - Configure your URL scope appropriately
- Click
OK
- Go to
Extensions > Installed
and reload the extension (uncheck the "Loaded" checkbox, and click it again) - Perform any testing in Burp Suite Professional/Community
- Export the session handling rule by going to
Session handling rules > Cog button > Save settings
{
"project_options":{
"sessions":{
"session_handling_rules":{
"rules":[
{
"actions":[
{
"action_name":"Custom Header Action - Random UUID Value",
"enabled":true,
"type":"invoke_extension"
}
],
"description":"Add UUID header to requests",
"enabled":true,
"exclude_from_scope":[],
"include_in_scope":[],
"named_params":[],
"restrict_scope_to_named_params":false,
"tools_scope":[
"Scanner"
],
"url_scope":"all",
"url_scope_advanced_mode":false
}
]
}
}
}
}
We recommend testing this extension in Burp Suite Professional/Community Edition before Burp Suite Enterprise Edition for easier troubleshooting. To test this extension in Burp Suite Enterprise Edition, you can configure an upstream proxy through Burp Suite Professional to view the requests and ensure that your header has been added appropriately.
- If you do not have Gradle already installed, follow the installation instructions here.
- Once Gradle is installed and you are ready to build the extension, run
./gradlew build
from the extension directory using the command line - Make sure you are using the latest version of Gradle.
If no changes to the code are required, a prebuilt JAR file is available under Releases. It is preferable to compile your own JAR file.