Wednesday, February 1, 2017


This release adds various new features and addresses some issues.

There is a new Scanner check for suspicious input transformation. This issue arises when an application receives user input, transforms it in some way, and then performs further processing on the result. Burp reports reflected and stored input that has been transformed in the following ways:
  • Overlong UTF-8 sequences are decoded.
  • Invalid UTF-8 sequences containing illegal continuation bytes are decoded.
  • Superfluous (or "double") URL-encoded sequences are decoded.
  • HTML-encoded sequences are decoded.
  • Backslash escape sequences are unescaped.
  • Unexpected transformations resulting from submitting any of the above payloads.
Performing these input transformations does not constitute a vulnerability in its own right, but might lead to problems in conjunction with other application behaviors. An attacker might be able to bypass input filters by suitably encoding their payloads, if the input is decoded after the input filters have been applied. Or an attacker might be able to interfere with other data that is concatenated onto their input, by finishing their input with the start of a multi-character encoding or escape sequence, the transformation of which will consume the start of the following data.

Various enhancements have been made to Burp Infiltrator, in response to feedback from real-world usage:
  • A bug affecting the patcher when running on Java 6 or earlier has been fixed.
  • A bug that caused the manifest files of some nested JAR files to be lost has been fixed.
  • A bug that left invalid signatures in place after the relevant bytecode was modified has been fixed
Burp Scanner's issues are now mapped to CWE vulnerabilities.

There is a new command-line option to prevent Burp from pausing the Spider and Scanner when reopening existing projects. To prevent this, add the following argument to the command to launch Burp:


Various other enhancements and bugfixes have been made.
MD5: b9371185454563e5ca279ab80d5fdd28
SHA256: aae6d011211313f9408de431c7ac3fe230d6d0d61c038add3778b453ad33e9b8

MD5: bb3592dd77027d583be6081988e48522
SHA256: 77740b44eebba7dce56cc866380a7cf94fca4536c22d14edb183d2f7f7a3177c

MD5: a572b5b026290335f8b5d2dac0766dbd
SHA256: 2bd6c8f09ad657716e95191ac4841297f268ca5ce279dd164b0d67ccd375683d

MD5: fc1bb251a9ec7685160cff3fcd5119e3
SHA256: 4b54fbe77bf8e89508316731f621ba03a25dd224fa7f3855e7a6db8dd653a5df

MD5: 8b40a5bdf55848329ca9f9eb9b3e7154
SHA256: c8c4c8cb3156d523e3f5630b0c1500df05eb4a0297bdcd23fb00e0853467bf7e
MD5: 408d063f42f51ea027bb6a5014ae58e6
SHA256: f18ad7d5873ca4fa29af04e8cd9ce967792377366b74edc5943014440f2cc815

MD5: 83d6022c7b739c346b14897ac491e8a0
SHA256: ea41d8afeb1f621ccfa15d56d4bb8a0a72d5fab3dabe4164696527ae692df4db

MD5: 1af427b18de46c38410b46fb5a3f8080
SHA256: 603ca7adb8561a73c6ce49c463c8e8bee36c9ae88422f53b9af5fe5136f80aec

MD5: 36567e3a4b010d981d477be97c924753
SHA256: ecc64b14e64225bd54429a283cc184f5febea93d1eac531cda302d2defcb48f5

MD5: b9c142ffff80cce82c54e3ed3ce17814
SHA256: 96fc23d40efbe386217ce71c33a68a31fa589f13443a25c2bb5842c55d6fca0f

Monday, January 16, 2017


This release adds various enhancements and fixes:
  • There is a new command-line option to launch Burp with a specified user configuration file:


    This can be used to set any user-level option, including Burp extensions to load. It is useful when running Burp on headless systems where there is no UI for configuring user-level options. By creating a suitable user-level config file, it is possible to launch Burp on a headless system with specific Burp extensions or any other user-level setting.
  • Some recent changes to Tomcat cause it to reject a wider range of raw characters in the URL query string, going beyond the standard practice of browsers and other web servers. Burp Scanner and Intruder now apply URL-encoding to the relevant characters by default, ensuring that their payloads are accepted by Tomcat and reach the application code.
  • A bug that was recently introduced that prevented license activation in headless mode has been fixed.
  • The Content Discovery function now correctly handles applications that have wildcard behavior for file extensions (e.g. those that return a specific response for regardless of the file extension). This eliminates the only known false positives reported by the new Content Discovery engine.
  • There are some new options in the Proxy for stripping request headers that offer to support encodings that may cause problems with intercepted traffic in Burp. These options are on by default.
  • Logging options have moved from the user level to the project level, and are now included in project-level configuration files and project files. This means that you can enable logging on a per-project basis and have this setting remembered when reopening a project file.
  • Unicode characters in URLs are now properly handled in the "Paste URL as request" function.
  • Various other minor bugfixes and enhancements have been made.
MD5: 6a1d1e734e9191b4eb8476b1da691597
SHA256: e2d30656bf3f6b51d48c212853ef0f1ab85a62850d398bfb40e616173eb2b023

MD5: 2ef30460b9609ff1c8692453a4f4ed35
SHA256: 9aa48e63d66e701a17db10bd47f12c899efc68213f4d32d29472e8ddd857fa07

MD5: e71679acf722df8f54a66df7bda1c5a4
SHA256: eda1e4ff9db2235cb2a3d2c7637c79d00387a862c82f839f042f4ee4d62b949a

MD5: a8d30d750458339a58165eda96a83b96
SHA256: ae0f3dd56005e5f7ea4e9addf4be448fcf50f321fb07148d9140d83a54f8b4f4

MD5: 60c970dc6830d1ad4a6080b88012d94f
SHA256: 655241b5da121cc34c7b3962f2d654cd029efebdc46aa6d80ceda7a6151e2019
MD5: 47d11b07fe7b385dd1001b326efb5e79
SHA256: 2acb901751a81411a73edd8e15bbcc5b8c6167faae491d88a8dced56747043d1

MD5: 4aea2396b922299976884414a0931dac
SHA256: 3e9ef1b58e9fd6aecde614b61a9a61f0a86f03ac123d1d81e11c60a5dd61252c

MD5: 647c2992b7c6bc463776a13439af2765
SHA256: a281b6101c0fbec7e07c9165a2865978a6c380f4471ff53d9256cba028b08c7d

MD5: af74d8e21dacb022f8ae76a65456c7e6
SHA256: 9187bcefbef1ea7a5ac6bbc9c76db8d0a53a8922c1251401775a8f6faf323c5d

MD5: b3962e75638ec65dcc17e4c6d4305989
SHA256: a7bb5f4a1af3ab27350d54c8567becd4c4ff96a79f0efb2bb951e67e7dae6f52

Wednesday, December 21, 2016


This release includes the most frequently requested feature of all time: custom wordlists in the Content Discovery feature.

It also massively improves the accuracy of detection of valid vs. not-found responses in the Content Discovery engine. We believe that this is now approaching 100% accuracy in terms of both false positives and false negatives. If anyone encounters a site where the Content Discovery function is not completely accurate, please let us know the details and we will investigate.

A number of other enhancements and fixes have been made:
  • Further to the security issues that were fixed in 1.7.14, some additional hardening has been performed of in-browser actions and the CSRF PoC generator, to prevent some conceivable attacks involving excessive amounts of socially engineered user actions on a malicious site. 
  • A bug that caused the Burp Comparer progress bar to intermittently hang has been fixed.
  • The SMTP service of the Burp Collaborator server has been modified to reject emails without a valid interaction ID. This effectively prevents the Collaborator wrongly appearing to be an open mail relay, which caused failure reports by naive security scans.
  • A bug that was introduced in 1.7.14, which prevented Repeater requests from being issued when a tab other than the "Raw" tab was selected, has been fixed.
MD5: 28fd91f8d490539f43f7656be183a2f8
SHA256: 5c6c92ba03f9949bdee5ad06de1857cf95b6a185472099714c35fe803493d5f8

MD5: 4dda1b4b6f5b2f6e26800d2de27cee81
SHA256: 4981643c399dd99f9466137e847802358ace1008fb0e6e427b9608453b97d494

MD5: 00805dcdc13a8980feeda8385d090ab6
SHA256: f1ed25e925b68bbc6c83a350a768e663e51d2cbd60e1a7ef5fa9a70a305928f4

MD5: 6c0ead0f72fe6b1d5253c704112fed7b
SHA256: 9a58431985e160676dee27f86d5d0122a946b576d69b8c9501ec095635179b8f

MD5: 5d4eda1c4081fb6569210fb33ddfe1e0
SHA256: 82d7224ddd9e645686141eb47380df90f6717221fde65f865e2696c47944b559
MD5: bffe16e37aece609df12f4db5ce4521a
SHA256: 06a412dc4c42ea25e6aa374f6b37485d64ebde297e40a2c30a8ade889c242e1d

MD5: 0f6025fe4a822d784796fe376554438b
SHA256: 8d8ad2bcf579dec1a78f8972e0ea79c48d5a107b87bf870627f529b5f2e1c4fe

MD5: 2c237465d7a56e06f36191566f0c9e7c
SHA256: 0fc1c1cfe9804277a4674e16ceb5ac564d24330eae085c660f6c8b9646315e91

MD5: 70fe127e99827df4c15453a89dc6afab
SHA256: 500f265c1726b7d87cba6ccdf24b4e173606c07c8c7a2fae83a96808375c8c86

MD5: ddb4e11c25f65403083cf4911f9c78cf
SHA256: d5816fa34f22c4d90e4903e756c52c925e09701a00941892848d24288678a57b

Tuesday, December 13, 2016


This release fixes the following security issues that were identified through our bug bounty program. Note that all of these issues involve the Burp user actively testing a malicious website that has been designed specifically to attack Burp Suite.
  • If a user visits a malicious website in their browser, and in Burp selects a crafted request that was generated by that website, and uses either the "Request in browser" function or the "Generate CSRF Poc" and "Test in browser" function, then the malicious website can XSS an arbitrary website.
  • If a user scans a malicious website and another website within the same Burp project, and exports all of the scan results as a single HTML report, and views that report in a browser, then the malicious website can capture the scan results for the other site.
  • If a user scans a malicious website and another website within the same Burp project, then the malicious website might be able to capture the raw data of any Burp Collaborator interactions that were performed by the other website.
We are pleased that our bug bounty program has alerted us to these issues within Burp. As well as fixing known issues at source, we have taken a defense-in-depth approach to hardening Burp in response to them, including:
  • Some functions within Burp's in-browser interface that increased its attack surface have been removed altogether, including the Proxy history, the buttons to repeat requests and view responses, and support for the plug-n-hack Firefox extension.
  • Scan issue descriptions, including those generated by Burp extensions, are now subject to an HTML whitelist that allows only formatting tags and simple hyperlinks.
  • HTML scan reports now include a Content Security Policy directive that prevents execution of scripts in modern browsers.
Note: The security issues identified have all been fixed within Burp Suite. As a defense-in-depth measure, some hardening has also been performed of Burp Collaborator. It is recommended that users who have deployed a private Burp Collaborator server should update to the current version in a timely way.

Thanks are due to @_Abr1k0s_ for reporting the aforementioned issues.

A number of other enhancements were made, including:
  • A number of improvements to existing Scanner checks to improve accuracy.
  • When a request is sent to Repeater but never issued, the request is now stored in the Burp project file, so the initial unrequested item will reappear when the project is reopened.
  • The Proxy listener now accepts SSL negotiations from browsers that are hardened only to support selected protocols and ciphers.
MD5: a7d25a036f8800876b0ea068c20aad74
SHA256: 850d7a319fd869f346435ff0cdf8f1e4be8cc6cb48c1e1873c5b6891d54ef16e

MD5: 127043d3efb121938d00df46b33475cb
SHA256: c2a9177e822dcb11c9b8135889bd5395b7f059d450e99e89c20b8e380c7aa479

MD5: cf7b9daf47cc691b71f8a9d0f7cf4ca1
SHA256: 5781caa88a5e5f24fbc69eb9c9a16923faa104f3962ebc6e309e5d1c5e4e1457

MD5: 6649ef1ec97760069c337c5ac2519e54
SHA256: 52c5539e099fbb1a09e3d7991f9122543ab22b3eb37250f5f304123378d3e6be

MD5: 56aacc5bd084284815f4cc4065536573
SHA256: b3b2878389bbd3145eaf2cd588e6f77ec9fc5dabd5cd9ea92d485d961ada5c9e
MD5: 5f5d41c2272b286e538ce262de638122
SHA256: f856708a42764683ad32aac14147b5b5dfc8a46e1ea896cdd152fd04c513eb0b

MD5: fe2f537e8857c85d15057c656a18109c
SHA256: a0dfd6655209712708194b37e33fb3d3b56589a0399ca0f17f4e3c24a204d72b

MD5: 3de7554ee093195b577ab47c556f86c1
SHA256: afa278687957f3bb8fad20d8f088b18fa0ffd399621ec891855fb1116ab42476

MD5: 91b9d62bf72b4de20cc18cf246fe8d12
SHA256: 64a25a8a79c69c0c6e2f59b654351333165f26af39fe7b044fb73f88c0818dc8

MD5: 132ad25dbde203ac9f0b09a4ca9bcba1
SHA256: 5dc5c9ca26bb1d4fef67b79fd77543fe8b854f85ecf2c1be94310b9c44f88314

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