Scope

• Website: https://portswigger.net/ __

• Web Security Academy https://portswigger.net/web-security __(certain vulnerabilities only)

• Software: Burp Suite Professional, Burp Suite Enterprise Edition, and Burp Suite Community Edition

All subdomains of portswigger.net are strictly out of scope. Do not test these.

If you wish to test the Burp Collaborator functionality, please configure your own private Collaborator server and test that.

Vulnerabilities of interest

Here are some examples of vulnerabilities that we could consider to be valid, and rough guidelines as to what kind of payout you can expect:

Critical - $10,000

• SQL injection on portswigger.net
• Remotely retrieving arbitrary users' Burp Collaborator interactions
• Unauthenticated RCE on Burp Suite Enterprise Edition

High - $3,000

• Stored XSS on portswigger.net or the Burp Suite Enterprise Edition web interface
• File path traversal on portswigger.net
• Complete authentication bypass on portswigger.net
• A website accessed through Burp Suite can make Burp execute arbitrary code

Medium - $1,000

• A website accessed through Burp Suite can retrieve local files from the user's system
• A website accessed through Burp Suite can extract cross-domain data from Burp's sitemap
• Given a collaborator payload, an attacker can retrieve interactions generated from the same key
• Exploitable reflected XSS on portswigger.net or Burp Suite Enterprise Edition
• CSRF on significant actions

Any medium severity issue involving unlikely user interaction -

$100-$1000

• Reflected XSS that is unexploitable due to CSP
• DLL hijacking on the Burp Suite installer, on fully patched Windows 7/8.1/10. This only applies to DLLs dropped in the Downloads folder, and other folders a remote unauthenticated attacker plausibly has access to.
• Header injection in Burp Suite

CSP Bypass - $100-$1000

• Content Security Policy is a significant part of our security so we will reward CSP bypasses through trusted domains, JSONP, etc. We are less interested in reports of hypothetical dangling markup attacks, and reports like "CSP headers are missing from static page X" but will consider these on a case by case basis.

Significant vulnerabilities in BApps - $0

• We will work to resolve serious vulnerabilities in extensions in the BApp store, but do not offer cash rewards. If you're searching for issues in core Burp, we highly recommend disabling all extensions first, to save yourself from wasting time.

If a report does not qualify but we find it useful, we may reward it with reputation or swag as a goodwill gesture.

Issues not of interest

The following are strictly forbidden and may result in you being barred from the program, the website, or both:

• Denial of service attacks
• Physical or social engineering attempts
• Targeting subdomains of portswigger.net
• Bruteforcing subdomains
• Spamming orders
• Unthrottled automated scanning - please throttle all tools to one request per second.

We are not interested in low severity, purely theoretical and best-practice issues. Here are some examples:

• Denial of service vulnerabilities
• Local privilege escalation
• HTTP Options header
• Server errors with no sensitive information like https://portswigger.net/careers%22%3E __
• Headers like Server/X-Powered-By disclosing version information
• XSS issues in non-current browsers
• window.opener related issues
• Unvalidated reports from automated vulnerability scanners
• CSRF with minimal security implications (logout, DoS, etc.)
• Issues related to email spoofing (eg SPF/DMARC)
• DNS issues
• Content spoofing
• Reports that state that software is out of date or vulnerable without a proof of concept
• Missing autocomplete attributes
• Missing cookie flags on non-security sensitive cookies
• SSL/TLS scan reports (this means output from sites such as SSL Labs)
• Caching issues
• Concurrent sessions
• HPKP / HSTS preloading
• Implausible bruteforce attacks

There are a few known issues we consider to be low severity, but may fix eventually:

• The embedded Chromium browser in Burp Suite 2.* receives non-critical security updates after a delay, and as such may have known vulnerabilities. These will not typically be rewarded unless you can provide a working PoC demonstrating RCE.
• As customer numbers are emailed out in plaintext, users should be encouraged to regenerate them on first login
• Generating a new customer number should kill all associated sessions
• Invoices, quotations and receipts can be accessed by anyone who is given the link. This is an intentional design decision to enable sharing (the ability to view someone's invoice without being given the link would be considered a serious vulnerability)
• Plug 'n Hack discloses the port the proxy is listening on by design
• Changing the proxy settings to listen on a non-loopback IP exposes the web interface to people with network access by design.
• Verified SSL connections should be stricter about which protocols/ciphers are tolerated

Some other caveats:

• The Paypal price can be tampered with but underpayment will result in product non-delivery so this isn't a security issue.
• We use Content-Security-Policy (CSP) site-wide. This means you will have a hard time doing alert(1). We pay for HTML/JavaScript injection regardless but to maximize your payout, see if you can make a payload that will steal some sensitive information.
• As the makers of Burp Suite, we can assure you that we have already scanned our website with it. Don't waste your bandwidth.

What constitutes a vulnerability in Burp Suite?

The system that Burp Suite runs on is trusted, and every system that can access the Proxy listener is trusted to access the data within Burp. Extensions, configuration files and project files are also trusted. Websites accessed through Burp are untrusted, so anything a website could do to read files off the user's computer, read data out of Burp Suite, or gain remote code execution would be considered a vulnerability. Also, any way to get someone else's Collaborator interactions would be considered a vulnerability. Burp doesn't enforce upstream SSL trust by design, so we're not currently concerned about issues like weak SSL ciphers that would be considered a vulnerability in a web browser. Detection of Burp usage, denial of service vulnerabilities, and license enforcement/obfuscation issues are all out of scope. Please refer to the payout guidelines for some example vulnerabilities.

What constitutes an eligible vulnerability in the Web Security Academy?

Our Web Security Academy __is full of intentional vulnerabilities including SSRF and RCE, and completely isolated from the rest of our infrastructure. As such, we are only interested in two possibilities: escalating privileges to root inside a container, and escaping out of a container entirely. These would quality as'low' and 'medium' severity respectively.

Contact

If you have any questions, or want to report a vulnerability without opting in to the reward program, you can contact us at support@portswigger.net

Good luck and have fun!