Burp Suite, the leading toolkit for web application security testing

Burp Suite release notes

Tuesday, November 29, 2016


This release adds various enhancements and bugfixes.

Burp Infiltrator has been enhanced with a large number of new API sink definitions, for both the Java and .NET platforms. This dramatically increases the coverage of existing vulnerabilities, such as OS command injection and file path traversal.

You can export the updated Infiltrator installers from the "Burp" menu in Burp Suite Professional. If you have already installed an earlier version of Infiltrator in an application, you can just run the new installer to update the instrumentation with the new API sink definitions.

The BurpInfiltrator.dll .NET assembly is now signed, and all instrumented assemblies refer to it by its strong name. This change will address some issues that can arise with usage of signed assemblies.

The manual Burp Collaborator client has been enhanced to give full details of Infiltrator interactions. This can greatly assist manual testing and exploitation of vulnerabilities, for example by showing the full SQL query that is executed when some particular input is submitted. Also, the Collaborator client UI now shows the Collaborator payload in the table of interactions, and supports user comments and highlights:

The IBurpCollaboratorClientContext API now supports separate retrieval of regular Collaborator interactions and Infiltrator-driven interactions.

The following bugs have been fixed:
  • A bug in the "copy as curl command" function which could enable a malicious website to generate an HTTP request which, if the Burp user uses the "copy as curl command" function and executes the output in a shell context, will cause arbitrary commands to be executed. There is no exposure to users who do not use the "copy as curl command" function, but it is recommended that all users upgrade to the latest version. This issue was discovered through an internal security review, rather than a user report.
  • A bug in the Burp Collaborator health check which caused SMTP/S connections made by the health check not to honor the configured SOCKS proxy settings.
  • A bug which caused Proxy match/replace rules to display as type "regex" even if they are not.
  • A bug where use of a partial/incomplete configuration file at project startup caused any undefined configuration options to have blank values. Now, any undefined options are assigned their default values.
  • A bug which caused Burp to leave temporary files on disk if the user cancels out of the project startup wizard.
  • A bug which caused items in the active scan queue in the "waiting to cancel" state to display in that state indefinitely if the project is closed and reopened. 
MD5: d77803b395e89359ce243db83a6f0b19
SHA256: 61f932686e199ade470ee7850e17c87798dc0ea36c30543e8cb57783e3728e36

MD5: a1b3edbf90dedebb9aff09833d576a62
SHA256: 8c53f3af171c4338af1777e2ed59481a135ccb04a2b747d739a6730fe67564f4

MD5: 39f627254197e64a5026bc2432468717
SHA256: 2f704124384bb8fe81ea6dc2e2a15a97dd349dbcee66d7f6999a8720bc657f3e

MD5: a3856f999d22265a70e76657e6e50bee
SHA256: a521df231d4471827d8028b79b7a4b821ffcb6ed872ae6362b25efb96f9eb50b

MD5: 1b066f7cfc92059904c5e756cad4817b
SHA256: 55e9bfeb31948a6f6403f20b1a0356e6f5a2af4e1175beadce3f038621def6d3

MD5: 290ecf4a30f15a9bded2ea86958e2f87
SHA256: a46680443dfae0b4c8e9cff2ce7fc40be6cf347b6dbbb6b140960f8c7551454b

MD5: 36826e7c67d74e39805131139709406b
SHA256: edb8351bd21980b30a2439e88603a4aae8907d18c552c1759eee15b24349446b

MD5: e34414aa760ae741e01f134eb08cdcd9
SHA256: 48ac90ae33c51be4576109a438422f67c77d5694e2e0cad8aea7bd29b4f18ad2

MD5: 09c2e95dd6421e1890c1c2b6f96d6a01
SHA256: 9c4dc164d20d224a3235cb78bf6932c85bda41d983589d9f742d7ccf36d9f0ea

MD5: 0e3bfa771ca43388329629eaa354cc79
SHA256: c95154eb56d295ad109165751e6842ceb7cf8ab69dc47e6c97d2b9799fbb9bac

Friday, November 18, 2016


This release updates the Burp Collaborator server to capture SMTP interactions, and adds two new related checks to Burp Scanner.

There is a new scan check for SMTP external service interaction. This reports an informational issue that identifies application functions that can be used to generate an email to an arbitrary address. This will typically (though not always) be intended application behavior, but it represents interesting attack surface for manual review:

There is a new scan check for SMTP header injection. This reports cases where it is possible to inject email headers, with the result that an email generated by the application is copied to an arbitrary email address:

For all SMTP-related issues, Burp Collaborator captures the full SMTP conversation that took place, and this is reported within the scan issue. This provides evidence for the issue itself, and also may contain interesting information about the technologies and infrastructure being used:

Note that users who have deployed a private Burp Collaborator server will need to upgrade their deployment to use the latest version, to gain the benefit of the new SMTP capabilities.

MD5: 163b26f266bbe93c8a7221e443e0f2a5
SHA256: 538d434c90e345227a104e23e06d1610945b36079899ab7f8d555e14b9480211

MD5: 0b9f924a7db0f2d128d3c86b27e29e79
SHA256: 2c456dc9d1ed8e1770536ecd2f52232a2d2642c37c744216382c236d21f63548

MD5: 5e5d7ee45ec4b453e7d1f9e08b813337
SHA256: 844e2732f137a6fff82983fd06af7a54f6bfbbc595b93be71b70208097c5643f

MD5: 2f2c9ab2089911b95b115f54c2cc6594
SHA256: 62ac35945dd995a69797255758d40acc6013009ddea70f784f0f41cb5fe13878

MD5: e3ac458fe4a30762ebe1b1b4694301ac
SHA256: 8e46719bccbc6750cb53c1dfa9b8bb90824f2381b38bcd09eebdebe6494623dd

Friday, November 11, 2016


This release adds support for the .NET platform in the Burp Infiltrator tool.

To use Burp Infiltrator on .NET applications, go to Burp menu / Burp Infiltrator, and select the .NET option in the export wizard. For more details, see the Burp Infiltrator documentation.

The new .NET version of Burp Infiltrator works in the same way as the existing Java version. It supports languages written in C#, VB, and any other .NET languages. It supports versions 2.0 and later of the .NET framework.

To patch .NET applications, Burp Infiltrator makes use of bytecode assembly and disassembly tools. These can be either: (a) the ilasm and ildasm tools that are distributed with the .NET framework and the Windows SDK tools, respectively; or (b) the ilasm and monodis tools that are distributed with mono. You must specify the location of the assembly and disassembly tools during the patching process. Note that the version of the assembly tool must match the version of the .NET framework that the bytecode is targeting, to ensure compatibility.

MD5: 707d6a1f09af1de03286628d2989640e
SHA256: 9ed9d0f3bff9a777599245266de6f304e2ab82d03b2703fabfaf2bb781b32b66

MD5: 778f62d8c36820172d41bc261617bb2f
SHA256: 590f4665b2f09dce3e0396888d58efce6b7459705ac9edcfdf552c6b661f3d8d

MD5: bd3e47d505186329daa7ccd65fcb4447
SHA256: 936d8ab8d8ca5545186763204d5f83e0961608037d26ba1c472ddad58f9dbd79

MD5: 915cd98a93bce088540bdb3255f35d67
SHA256: 9a103b0666fecab997dec65779a5ea4cbb88c2c1a00b209eb8923647c8f91c7c

MD5: 98951da5d8e3280b4025e48dd189ec9b
SHA256: eda87ba8e143c3abc505d432d5e7643497151683f5e2081605296a9d853c1631

Wednesday, November 2, 2016


This release adds some new APIs that extensions can use to easily implement powerful scan checks and other logic that involves response diffing.

Two new APIs have been added to IExtensionHelpers. The method:

IResponseVariations analyzeResponseVariations(byte[]... responses)

analyzes a collection of responses to identify variations in a range of attributes. The IResponseVariations object that is returned can be queried to determine the invariant or variant attributes, and the "value" of each attribute for each response:

List<String> getVariantAttributes();
List<String> getInvariantAttributes();
int getAttributeValue(String attributeName, int responseIndex);

The attributes that are currently supported are as follows:


Note that all values are represented as integer numbers, and the values of some attributes are intrinsically meaningful (e.g. word count) while the values of others are less so (e.g. checksum of HTML tag names).

The method:

IResponseKeywords analyzeResponseKeywords(List<String> keywords, byte[]... responses)

analyzes a collection of responses to identify the number of occurrences of the specified keywords. The IResponseKeywords object that is returned can be queried to determine the keywords whose counts vary or do not vary, and the number of occurrences of each keyword for each response:

List<String> getVariantKeywords();
List<String> getInvariantKeywords();
int getKeywordCount(String keyword, int responseIndex);

The new APIs allow your extensions to let Burp handle the messy work of analyzing responses to determine if they are the same or different, and you can easily create powerful scan checks with some simple logic:
  1. Send novel payload.
  2. Ask Burp whether the response changed in some interesting respect.
  3. If so, report an issue.
On Friday, to coincide with our Backslash Powered Scanning talk at Black Hat EU, we will be releasing an extension to the BApp Store that demonstrates how the new APIs can be used to create powerful new scanning capabilities.

MD5: 64ae656dd589f1db2d3d47452e705318
SHA256: 6319c21bd790408d475ca63258966df111eb5ab414e8a6a5e0f4bde530ea65f6

MD5: 635d0684503e0ef5208dc74355647ae8
SHA256: 65e5054d1f6cde2610ead300d7847be315445d08b18ddd756fbe75e5b8578d3c

MD5: d34753e71e8fcd505e39510c6bf9e74b
SHA256: 9f609d14d474f43c9261c920c4a868278cbac119fcee62a328274e093738378d

MD5: a1ba61e1d546119d224200484ac8cf95
SHA256: 98736d7f2c6dc10b02ab2500674ee9da8cd242c5e23985aa6db308772ca1fdbf

MD5: e6c87ea96bf26e1d626f9a60d3432853
SHA256: 683829438af4b46c150f06ad434e8dcea4d8a831dfe92b74f2d13a3468122d94

MD5: 91a01d4c012b0d20c247d448de897f1c
SHA256: 1c7c86f939eac526fac76f39c9d18bd1900ad68248a39b229f367adae56c0458

MD5: f616c47bfcb8d3f4d9969da7dd20689c
SHA256: e605812b52480fd07b42295558867642a4d58d6827d61b4b97299f84875bb985

MD5: 0e7fe55599593c4308fd35b535cbc182
SHA256: 1bfcea1de60fdcd0b5e9d0271e92b34c3621e31e12ed114d3b599500b9168f94

MD5: 35e4ef35c1718a79eba8ce1fd311c854
SHA256: 63bdc696553cc9430110a0fbaafb493b925b9d53a0bbf85cda3448903cb6a179

MD5: fa60402b162ba509c6fca88961d6cbd7
SHA256: ee8156764423de5a6f65ff3683cf5b7c200769a5116ecb050abaa84de1ada950

Friday, October 21, 2016


This release adds a new Burp Collaborator client for use in manual testing, some new APIs for using Burp Collaborator capabilities within Burp extensions, and a new Burp extension that demonstrates usage of the APIs.

Burp Collaborator client is a tool for making use of Burp Collaborator during manual testing. You can use the Collaborator client to generate payloads for use in manual testing, and poll the Collaborator server for any network interactions that result from using those payloads.

To run Burp Collaborator client, go to the Burp menu and select "Burp Collaborator client".

The following functions are available:
  • You can generate a specified number of Collaborator payloads and copy these to the clipboard. You can use these in manual testing, for example using Burp Intruder or Repeater.
  • You can choose whether the generated payloads include the full Collaborator server location, or only the unique interaction ID.
  • You can poll the Collaborator server to retrieve details of any network interactions resulting from your payloads, either at a regular interval or on demand.

Some new APIs have been added for using Burp Collaborator capabilities within Burp extensions. There is a new method on IBurpExtenderCallbacks:

IBurpCollaboratorClientContext createBurpCollaboratorClientContext();

This creates an IBurpCollaboratorClientContext object that can be used to generate Burp Collaborator payloads and poll the Collaborator server for any network interactions that result from using those payloads.

To demonstrate usage of the new APIs, we have today released to the BApp Store a new extension that can detect the HTTPoxy vulnerability via Burp Collaborator.

The source code to the HTTPoxy Scanner extension is available here.

MD5: df736dbf78bb7fcc26d58f1fa814217a
SHA256: 4d44459c04421c934f0c8e60618e255bd913213ab88021d9eee6f651949bc389

MD5: adad04d39abf937bc7c3fb6f29f28297
SHA256: 629b0c6748b115daa8dc2f31db8c7809485fc6565b82b3b08b1fa6b64bd106ad

MD5: 96a2c68f76cdbe557cada92cf6363359
SHA256: 3df6b8da0a30489368cb9c532185020f4a72ec14f824f8a86072c4ff4c9d4b53

MD5: 1278ef18097e93702371972a5dffc1d8
SHA256: af405f2c2caeff869da58bcdd27b76ad1544b16a6fcbed0f39bfe42173fa3b41

MD5: 2ab5e0e558974ed4f631e6c3c20d2a55
SHA256: 27db96f7bdb6fdb477d77add896f562fb21f819fae7a3144b49aeca3e4c51ab8

Friday, October 14, 2016


This release considerably enhances Burp Scanner's logic for reporting issues with cross-origin resource sharing (CORS) and introduces three new issues:
  • CORS: arbitrary origin trusted
  • CORS: all subdomains trusted
  • CORS: unencrypted origin trusted
There are many subtleties with CORS configuration that are not widely understood but can lead to catastrophic vulnerabilities, as described in today's blog post. This update puts all of the knowledge from this research into Burp so that it can accurately report all of the different problems that can arise with CORS.

MD5: 41d7091e6f726b054a94336eba590eb8
SHA256: 27e53041de128ee92b7faacba6808800bb2be9d4fc827cf62484a5bfb1b6f314

MD5: 56e86cb01563730c6a59bea150dcf8c9
SHA256: 7320d6fdd4192fc34be0b72ce63df09e9c468c5f92a69ac0efaf038d5139b4ff

MD5: eb98fc4432cff3e288afd2bd2b6b3661
SHA256: 5b20bc2f1b236af3049a155fa8f122f5d91097041ebf17964bd640aa439ecaaf

MD5: 7301606590748be43d37a9080d78ba8f
SHA256: fa35a1c19ef7277540b367c36273096e92c97728317e1620a2cb836b76ecfe76

MD5: 22e4f0913a94c734e4083a8dbcc7a01d
SHA256: e3e78068f87f28dd4421d1cc0e9d8f74bfbcd32502300871ee2bf5fa648437cf

Friday, September 23, 2016


This release contains fixes for some bugs affecting a number of users, most notably:
  • A fix for a bug that caused excessive CPU consumption during active scanning in some situations.
  • A workaround for an OpenJDK bug that caused the JVM to crash when working with Burp project files on some Linux platforms.
MD5: 3f36c29637c99e9426718a74746b0aa9
SHA256: 8a337214b126e50f1d2b2055a35b7b80ea54601df70458d3b7e69af213e92c5e

MD5: 94f6e88ffc0c57a0f3ebd6bb7307236a
SHA256: 90a99549d93c15bc6ce2d33c5fd35adbbe403c3a1f8ca8eed2a32854ec60afb8

MD5: d1612f9172507f5d31e2271369529a5c
SHA256: e8473675ca256a0a2dcf13498481543f360881c1949db78648248d656ec6ca70

MD5: f210b5d81632ccf0aaaa566bf728c7e4
SHA256: 0cd3d4c4f3e469ba18a356521c982206b1785c0cf51405bd602ba1a0418698f8

MD5: e7569b00c2947ae71852f8483e85a785
SHA256: 080521f6c24a60eb0c67c583c59692eb0eec75ffe7d14f8885ac6afa62fa1ffa

Thursday, September 8, 2016


This release introduces a new scan check for second-order SQL injection vulnerabilities. In situations where Burp observes stored user input being returned in a response, Burp Scanner now performs its usual logic for detecting SQL injection, with payloads supplied at the input submission point, and evidence for a vulnerability detected at the input retrieval point.

The release also fixes a number of minor bugs.

MD5: b3296c14edbd8e118dd398259de15e5e
SHA256: e1412249fecdfb1fe3ac6d71920a2e243bec257f4961df5c37ab17f0f37ddaeb

MD5: 1191db44110714272fb474784b3d4dd0
SHA256: ce2da473fdb65f4704ad6597dcd6615ec84e7a4c3c81deaf4f2de360d362a9bd

MD5: 1385fa0625448329a8bde17d78b22f62
SHA256: 749e3d23d1d486c823d189da155d5637785de9ff6c5763f23fb54aa128e8a38f

MD5: 3cb9c69c9b589729ed46f75a7eca215d
SHA256: baa558f4754254ac2d7b9e94e6326929f8ac4553c60290d071a328a228573614

MD5: 05c1b4a8105d4e3d54d440ef89f0a8a3
SHA256: cba0a84144804fcc57ebb7a947c52aaee58452f14664e1c2c8ea8890f1ad1c12

MD5: 3f076d7508486ed8ca2045da47c482e1
SHA256: 4e92d57071c2402a471bff2684c056425dd32da2d97ed53682ac23d40f33c3a0

MD5: 71e8b517945a5a942b95b4fd01240505
SHA256: b1102ff98d7d4708e79028a0fa379e5e153b57645c2605c59eae28eabcd2fcc5

MD5: 738ee3c774c4ad9e3aefaaa4b4e6784c
SHA256: 185a86d6698c1da4224536a44c2ec2566226bc6c2399ab5b2ddb6f23539ed13f

MD5: b733aecf1678ca6352c6377e2a43a339
SHA256: 36f3c9e587f25bde066477c6a9e84fb3bc06fbae50e20c64de2a84af206377da

MD5: 4eea896f832ec4f0fcb93c4a0fe27040
SHA256: 873589bb08749b65ac9c4a47b11d00d94472fcf1dd08ff1756813e8a758a3b00

Monday, August 22, 2016


This release introduces native platform installers for Windows, Linux and OS X. These install Burp together with a private Java runtime environment, so you don't need to worry about installing or updating Java. The installation of Burp is fully integrated with standard OS features (start menu, dock, taskbar etc.), making it easier to launch Burp without use of the command line.

Pro edition users can obtain Burp platform installers in two ways:
  • Log in to your account and choose which installer to download.
  • Use the existing update feature to obtain the latest Burp JAR file, run that, and choose "Download other installers" from the Help menu.
Free edition installers can be obtained directly from the download page.
Note that although the platform installers have been extensively tested on various platforms, these are officially experimental and we welcome users' feedback about how they perform in real-world conditions. We will continue to distribute plain JAR files for people who prefer those.

There is also improved handling of updates. When an update is available, Burp lets you view full details of the release, and choose which installer type to download. When a release is flagged as beta, you can choose whether to download the beta release or the latest stable release.

A number of other enhancements have also been made:
  • The performance of the Proxy history view filter has been considerably improved, and changes to the filter are applied much faster on very large histories. 
  • Some instances where redundant data is saved to Burp project files have been fixed.
  • The options to select font size now permit selection of very large font sizes, as a workaround for lack of proper support for HiDPI screens on Java 8 and earlier.

MD5: 4f1b6f84c35c8b500cbf3085c382d797
SHA256: 88fa1d45493d3a835c97de1d63bcccc8bd94644eba64404044ba29390aae702e

MD5: 2a0a142e82b90813023707d611686f56
SHA256: 2ba86b92440c68dc9b9c9fc8af5de3e095cdfed3fc668f01064f8f475ad98740

MD5: d126dd11dc58fc1040bcf12f39966232
SHA256: c41894cce04a194fcb73ef0760bf9300fe283400a39b1f757d15827f68db94ad

MD5: 6d95586b8798a1e84692557ea87270ff
SHA256: 1430a8c481d1e7979719c9816a2f273529bef72bef46625d61ebfb30f8edb62e

MD5: 9066f94d41f4caf90756308be373ff7e
SHA256: 82c704200030ec941331baea1ec3948f0bfb4b1265410550df286a1102efaac0

MD5: 703f19226b8e53617d383b367f7fb437
SHA256: aa1d443288bc08112e556aad4959d1f81c3ee0d375d04efa2270fcf0fe03d514

MD5: c3aa1ef36ed80d34372f89be4b05ab03
SHA256: 3cf5c69130e95c2a3ea396d2c946b406d4448a1d9efe16be8b7d4adfcadf43d7

MD5: 471cc3470f2a80a7a02f345365c5603c
SHA256: ebcb7ad6732485569b36c145a4b99643056fc358c16ba1630a25f68b1e214c92

MD5: 3e29f6c7bc6a40fb456fce046097cc38
SHA256: dc023f8de24915fb52171d213f151499ea739a369d3646a469455dbe901c54a7

MD5: c1c4b842fa538f8c72c6171b669ddda2
SHA256: c0c303037432890921cfeed32cb428b1f7eb13ca8c7276eaeda5fb89e06b40df

Tuesday, July 26, 2016


This release introduces a new tool, called Burp Infiltrator.

Burp Infiltrator is a tool for instrumenting target web applications in order to facilitate testing using Burp Scanner. Burp Infiltrator modifies the target application so that Burp can detect cases where its input is passed to potentially unsafe APIs on the server side.

The initial release of Burp Infiltrator supports applications written in Java or other JVM-based languages such as Groovy. Java versions from 4 and upwards are supported. In future, Burp Infiltrator will support other platforms such as .NET.

For more details about how Burp Infiltrator works, how to use it, and some other important considerations, please refer to the Burp Infiltrator blog post and the Burp Infiltrator documentation.

Burp Infiltrator makes use of Burp Collaborator for its communications back to the instance of Burp Suite that is performing scans. To support this, some new capabilities have been added to Burp Collaborator. Users who have deployed a private Burp Collaborator server should upgrade to the new version.

Some minor bugs have been fixed, including:
  • A bug which caused the values of some project options to change when an existing Burp project is reopened.
  • A bug which prevented editing of macro requests when using a disk-based project.
  • A bug which prevented the hostname from being correctly parsed from some TLS client hello messages when Burp Proxy is running in invisible mode.
MD5: 85ab62c473e2be60d8da15ccc0c80cde
SHA256: 43fede912099ff0af99ac595ca45b56aef3af4a5743c5b5d3107ed170da74551

Support Center

Get help and join the community discussions at the Burp Suite Support Center.

Visit the Support Center ›

Copyright 2016 PortSwigger Ltd. All rights reserved.