Support Center

Burp Community

See what our users are saying about Burp Suite:

How do I?

New Post View All

Feature Requests

New Post View All

Burp Extensions

New Post View All

Bug Reports

New Post View All

Burp Suite Documentation

Take a look at our Documentation section for full details about every Burp Suite tool, function and configuration option.

Full Documentation Contents Burp Projects
Suite Functions Burp Tools
Options Using Burp Suite

Burp Extender

Burp Extender lets you extend the functionality of Burp Suite in numerous ways.

Extensions can be written in Java, Python or Ruby.

API documentation Writing your first Burp Suite extension
Sample extensions View community discussions about Extensibility

Wednesday, March 28, 2018


This release significantly improves the effectiveness of project repair when project file corruption occurs. Some users still experience corrupted project files when using virtualized file systems (for example, using Burp within a guest VM can lead to project file corruption if the host OS terminates abnormally). Previously, if some key metadata near the start of the project file was lost, then Burp's project repair feature would not recover any data. In the new release, uncorrupted data within the file can still be recovered even if this key metadata is lost. Further feedback is welcomed regarding the effectiveness of project repair.

To support the new project repair function, changes have been made to the Burp project file format. The new release is backwards compatible with project files from all prior versions, but project files created with the new release cannot be opened with older versions of Burp.

Some bugs have been fixed:
  • A bug in macro configuration where some settings for cookie handling might not be saved correctly across executions of Burp.
  • Some minor bugs in the automatic project backup feature that was recently released.
  • A bug where extensions could still gain API access to the Burp Collaborator client even when the user had disabled use of Collaborator.

MD5: a5fe57f8e6ef9c4b569629d5e96af092 
SHA256: 75d088a49548dfe790fa253e48aaf4da771878f935594f9a86c1c155fd92c4c3
MD5: ec5d448a642d9e1da2490e71d33270f1 
SHA256: d22f3f8c18ddb03f4a98244051cf0a9715b23edbc727a95a3deae6d073027a9a 

MD5: f37a7895e0dc811f61c19c37cd7e2165 
SHA256: 2d272773154e28140753ad4065666e1ecafdf63cf3c5b097d23b7d6ad1e1560f 

MD5: 274f8deb72af2bd4bbfe1b4aa6259404 
SHA256: 42161cffda8f131ca139ca449495d4490c10c8b65cc6aeaa5e0bea225ba9dff1 

MD5: 5404d47053587b1bcc6262937ae5678a 
SHA256: 5caf407e5ea11ba83fcec9a7314fba3d3760604f83f520202c8cbc5a745335e0 

MD5: cb6e5a00979463a2be634b6d5388bc49 
SHA256: 44bb6811f838aa6e3a47b0dc0d4ef5f7fbddc031ca5efe2d8bb5f24eb105dc12
MD5: 4a4c9834e066fbba863cfd06226a6747 
SHA256: 200f65fa118a1a11f05b0871b80ac871e19e4ea944dc7745678c6f42be349901 

MD5: 8ffc147bbdf76c45ae2f5412656c18f4 
SHA256: 0b18689e3ad6281ecf6fbc5201593ba8606c930c4dd95e27ede7dc9b79859c11 

MD5: e9b3def4b7d7cfa08a8d1d9c1ccb4b25 
SHA256: ebb3fc0f4f697ecd22a4074a87ca14fe387c775fb13e6cfe5ba8e4cb3ff2b82d 

MD5: c8ff3bf3fd51bc6d31e5513d6ff963e9 

SHA256: 1b2e3226ec8d5e4996e90939af004f3405c431d5d9210151d9060c05c66d7b02 

Friday, February 2, 2018


This release adds a new automatic project file backup function. If you are using a disk-based project, this function automatically saves a backup copy of your project file periodically in the background. The options for the new function can be found at User options / Misc / Automatic Project Backup:

The new function is superior to the older function that saved a state file backup in several respects:
  • Project file backups are considerably faster. Project files of 1Gb in size are typically backed up in a few seconds.
  • You can optionally include in-scope items only, to reduce the size of the backup file.
  • Available disk space is checked before performing a backup. If insufficient space is available, the backup is skipped and an alert is shown.
  • A single backup file is saved alongside the main project file. On successful completion of a new backup, the previous backup file is deleted.
  • On attempting to open a corrupted project file, Burp checks if a backup is available, and if so offers to open that as an alternative to repairing the original.
  • By default, the backup file is deleted on clean shutdown of Burp. Since the main project file is saved incrementally in real time, and project file corruption is typically caused by abnormal termination of the OS, it is not normally necessary to retain backup files following a clean shutdown. You can choose to retain the backup file on shutdown in the automatic project backup options.
  • You can optionally disable the progress dialog that is shown when a backup is performed, so you can continue working without interruption.
  • Backups are enabled by default with no configuration required. If you don't want to use the feature, you can quickly turn it off using the option that is shown in the progress dialog:

Other enhancements include:
  • Installed BApps are now updated automatically on startup. We issue frequent updates to BApps and it is highly recommended to be using the latest versions. You can disable automatic BApp updates in Extender options.
  • A bug in the import project function, which omitted to import the Scanner issue activity log, has been fixed.
  • Requests made by extensions during custom scan checks are now correctly reflected in the scan queue request counts, and are correctly subjected to configured request throttling.
MD5: 7e2383db4fb8d341e2dcd345b201d016
SHA256: f97e6926945df072606337fa53e53b414e2390c48164c51442f64c912b7b0048

MD5: e4dc384b8c819e3f316e9822fb177435
SHA256: a9a52bdf51bb7585f92b9b437512de5de7b00dd981cc58f4a9173c32bace7195

MD5: bde0236d51a550f0746cdb93d0e79716
SHA256: a63abbbba8ab20b20ca0c25032d7f1ea3bbc727d662f1726aea6e7d78e415e01

MD5: 0ba21ef9487cbac9b1635709337b3ffa
SHA256: 47a2e83496a4e1586c966c90d520fa4a541d468bbbcbdfebbf2a2b3289c76556

MD5: 460b75f1c104e7678b2391689077b291
SHA256: f6ebd51316d0f4a99de62cbf006c830c78f4ce09b2154d1e0c1fdf68d4911f7d
MD5: c54123915eb1c35ecf811263aa7962b6
SHA256: 9d76629d4f590542f6e02546b08ef0634ae006e83cd1678401a38e62eb909717

MD5: 3c0e4c2a2db783a92e04fa66ae15eb73
SHA256: 02abd2138f909c35523b7614525a7ed747b62560e4e275ff293798198e79dfd8

MD5: d4d43e44769b121cfd930a13a2b06b4c
SHA256: 49c719e86611ccfdcda8cd23fac8edb236369dd8d0e7133068eaf40315e52206

MD5: c984c818af04fe0ee96a9516769f07cb
SHA256: 09321cda391064d3739ac7092b2643f5aec3eb93846ab9fa446793938e817ff1

MD5: a7b889ff9284e9f1ffe2f269c5bb822a
SHA256: 8b83e3eec6bb2316ff5e8a19b92eda7e46f6a2103d412046d7916a488301ed56

Friday, January 19, 2018


This release adds two new capabilities relating to Burp project files:
  • You can now import project files into another disk-based project. This lets you merge multiple disk-based projects into one, to consolidate work that has been carried out separately. You can access this function via the Burp menu.
  • You can now select project files as input to the compare site maps function.
Additionally, the "Number of threads" setting in Scanner options has been changed to "Concurrent request limit". This paves the way for some major enhancements to the Scanner engine that are in the pipeline.
MD5: c44f168072bc99b9f49a33f53945390b
SHA256: da76d0533bf34d51f34020ec08fd45621c598f623332c4eae5b584d5a93d86fd

MD5: eee90447d19e244ac73e60faadbc1e8d
SHA256: e32ce5b386a00e6de0dbb2d670869e11185cf62ff57ee0c10517ab8288a7a3ec

MD5: f29ae39fd23f98f3008db26974ab0d0a
SHA256: 84bf3cbae91c621e4fb3c411409293e7759ba2b7ff3d2de4a1749383afcc6b90

MD5: ab66b33f01859405988ad08e9e0eab31
SHA256: f06e51714b35d217b3a4e461e4de424d148158b4ef0eeb1148647c3ed637954c

MD5: d2b30e984737501c66e8f4fc39db9e24
SHA256: 060734050997cda6635248fe9532cd2c824042f142ce71e7462c644dd6533afb

Tuesday, December 12, 2017


This release adds new granular configuration of scan issues:

You can select issues by scan type, and active issues are now subdivided into light, medium, and intrusive, based on the nature of the scanning activity involved in finding them.

You can also select individual issues. Whereas previously, you could select broad areas of scanning activity (such as "server-side code injection"), you can now select each issue individually ("PHP code injection", "Perl code injection", etc.).

If you select individual issues, you can also select the detection methods that are used for some types of issues, using the context menu:

This gives you highly granular control of the checks that are performed by Burp Scanner, and lets you create customized configurations for all kinds of specific purposes.

There are various other minor enhancements:
  • A "cancel" button is now shown during long-running filter updates.
  • There is a new option at Project options / SSL / SSL Negotiation to disable SSL session resume.
  • The "Copy as curl command" function no longer ignores any request headers. In older versions of curl, attempting to set some headers was ignored, but this is no longer the case.
  • A bug that caused automatically added SSL pass through entries not to appear in the UI config has been fixed.
MD5: 2d415e17f8bd99da3eb13a24b49bfba2
SHA256: e23cea82a18a1802ee0a9b95e6f4c4252cb42d02814296c438fc51a4e427c417

MD5: b380b4b12d1fec74fb7543c173b41b88
SHA256: abca4f8aaaf07b58692f3b12c5b3dd2e1d3e6e655c17691f99644bf799465f4d

MD5: 7c574f9cdb533b9e7e8c067d8c106db7
SHA256: 71b6f074e5c591247f043286e4b1b3a236b151c75ab7baae475c87d8485ef759

MD5: e75a5536122a2f5bb885fb8993e0ec88
SHA256: 9613c3bdfe53a17c2a0b3140aa9da78fbed6aa0e7cccc6c74dbe505991ae42aa

MD5: 1419145ca7d2a6da477363ac6f4a26e1
SHA256: bae9ce69491c20167a07d5efcbc2a1751ad83eb7b335d190d72ab8ac629f1b22
MD5: ad4afbacde19270b37aaff2336c4ae9f
SHA256: 9b5656905afbbd5f7a03197f9445d2aa9a0de14cabe5bd25cad6ec3093a47482

MD5: 283d8cc624e780abdffd89e558d392d1
SHA256: dd938718ba21e48bd07195f4bf074b0d249c8a3b56ba257d2e65674c8cf448a7

MD5: b20ee3a6d3195739c9dfa42d3db094cb
SHA256: 13e9210504c1a3c99d7d7c33c9a5b437f7845dd0d5929101a045c84a7b571d52

MD5: e0933d8cc9821fe9047218a464782d8a
SHA256: b5547c7fc6ce30870e47cb3e0cee20e17acbc3ff0f172c1917edc044d6c08422

MD5: 4253d70211421ea3e73ccc04f84bc720
SHA256: dbf9c831101ffab284d67f802b5fc7b920acaad9f596778615f369a39b5b1010

Monday, November 20, 2017


This release fixes a bug that in some circumstances caused the UI to hang after installing a new BApp.
MD5: aaa7b51924908481e72e32e5e1ce23fc
SHA256: a27d63bd2b1a91a59cd73ba413e742e553acd8f1235f77a5d76e6880b334e23a

MD5: 0b033bf218cc142368c624dd9e95347b
SHA256: ec475c8cf7e4b70f73ff53b3e5630bf9adcda033cb05552e266b54ffda514b2e

MD5: fd9710fd1725bfb9d9b5ccbba143a46a
SHA256: 5a1972cae097777e087acc20dae8a354f7450d25ec13fc4b6e10f57b1c4c4200

MD5: ed564ff8629732040c3105a65d3d8372
SHA256: 34e4ec423fd298bc5d0d0a8e73b989cbe7edde061ab41abe94ab53a94f4a9631

MD5: 0a7279ed37487e4b3cdd1242f4ee62ae
SHA256: be2b9cdd84648437b92e6702e01435d27764d3d8991904beff393b998d73dae1
MD5: e354845b4cacf6ae4c0621c23885c24d
SHA256: 376f65f5599c0131c539a4f20a55e5e41f0e4386188b3bb14ca4970edccc945c

MD5: e75f8c499e228bc55b13d41f0ef0c52d
SHA256: a9f33093b476b771a9fb1548e304bf134e916b88b28363ba965de6a93127e6f7

MD5: b5433f10a9022bf20429ce0d85b54e98
SHA256: cd6d9d03d5db4749e9fe52fb998978d401202eaca3d30cedc4c374d30e297dab

MD5: 3f9c1cee595e7cf3124af2b6862a33c7
SHA256: edf675b6d576cde168594a13500b05eb851faceb8a04c980294d7e1a2e9cfd00

MD5: 58c1eb6babf578f301ffcbc244b893e0
SHA256: e090c55f757560754f678b1f4bebb438909470ce56f86cad21917a1cc34ff113

Wednesday, November 15, 2017


This release introduces simplified scope control.

Burp's existing scope mode employs complex rules allowing you to specify each component of the URL individually (protocol, host, port, and path). You can specify each component using simple expressions, wildcards, and regular expressions. These rules are sometimes complex to create and interpret, and are computationally expensive to apply.

The new scope mode uses simple URL prefixes to define what is in and out of scope. Wildcard expressions are not supported. However, you can omit the URL protocol to match both HTTP and HTTPS:

The new simplified scope control is flexible enough for most purposes, and is enabled by default. You can still enable advanced scope control if you require the power of the old-style scope rules.

State files no longer support saving and reloading of project options. Only project state (site map, Proxy history, etc.) is now included. You can save and reload project options via project configuration files. State files in general are deprecated, and Burp project files should be used instead.

A number of bugfixes and enhancements have been made:
  • A false positive for external service interaction, from certain Collaborator payloads placed into the URL request line when using an upstream proxy, has been fixed.
  • Burp now includes the SNI extension in SSL negotiations even when the hostname doesn't contain a dot.
  • Burp Clickbandit has been updated to fix some issues on Chrome and Edge.
  • The BApp Store tab now shows the popularity, date of last update, and link to source code on Github, for each BApp.
  • A bug in the sessions rules UI, where session rules' references to macros were not reflected after reloading settings, has been fixed.
  • A bug in the filter UI, where a entering a long search string caused the text field to outgrow the window, has been fixed.
Burp's colors and graphics have been updated in line with our website. Additionally, the free edition of Burp has been renamed to Burp Suite Community Edition. We are planning some brand new editions of Burp in the future, and the new name will sit better alongside those. It will, of course, remain free of charge.
MD5: d1525fa91a378932f314f271b94a3b1b
SHA256: e26c12ab11914e5d73d3bcd8e9578b789c59ee87200845136f9b6d5a238074ac

MD5: 973151867335371aa686e44996961ec6
SHA256: ba1aad6c20104db4d14d4bc6b48302d4099ffac3180942b0b090831b25df76f8

MD5: 762443b04893cbbce69b5e30ec01e156
SHA256: c2e8224c2b32eca82e3fe8b08c498ce201ac4aba911ab3caafc9e521cd8f8b2a

MD5: d91ccdaa68841977335c0bb714eba3cd
SHA256: 31e627fd936510e8180238e8061069d9a614cb3d20479ebf50302a1152fd9707

MD5: 80f25bf5100d3d44ce78970e147c8b96
SHA256: 62055dd967a6ca352a7e661aebe1c0300c61db94beab2f2f9fd3711c5204412d
MD5: 89672c80f81a35f3db1fcb9ae4b5260d
SHA256: 3c80d0643812946c6fac98bcc2cdfe898bc7f596ddf96605ffc81ee2ec9a246b

MD5: b8039f9228f9071fae50695de6ad7af6
SHA256: b1a915f8c9893c410cd010547fdc7ded1bff42648e767f6775223624afc56794

MD5: 11595cf3d7f1e2db998bae4309ea2b03
SHA256: 3092692f47c396fa81d5d536a0108b91e10599fe80c12421937175be3bedc401

MD5: b2446f640421a8c5902ab0427df45c06
SHA256: fc15ada5132d452d95a2ca79f9bdafa160a8d8eae6e64ca677db749b8eccb2a2

MD5: 7d9cc726717f83166266f4da6e4da173
SHA256: 6070248eac93d0fa52708a5bd8d8a1d2660fb933e9f1dde1e95eb8e7b8fa8e9b

Thursday, August 31, 2017


This release adds various minor enhancements:
  • There is a new hotkey for adding an Intruder payload position marker. This is not mapped to any keystroke by default, but this can be done at User options / Misc / Hotkeys.
  • There is a new option on startup to disable extensions. This can help resolve situations where a misbehaving extension causes problems during startup.
  • Burp Collaborator server now responds to DNS lookups containing the subdomain "spoofed" with the IP address This is to prevent the Collaborator being wrongly incriminated when a server being scanned is vulnerable to client IP spoofing, as happened here.
  • The option to strip the "Accept-Encoding" header in incoming requests to the Proxy has been modified so that it normalizes the header to a default value rather than stripping it altogether. The previous behavior caused problems with some WAFs configured to drop requests without this header.
  • The default max heap size requested by the platform installer has been reduced from 75% to 50% of total physical memory, in order to prevent OS performance issues on some platforms. This can be modified after installation by editing the vmoptions file in the installation directory.
  • MacOS App Nap has been disabled as this can cause Burp's automated activity (like scanning) to be suspended when the Burp window is in the background.
Additionally, a number of bugs have been fixed:
  • A bug that caused temporary data saved by Burp extensions and the sessions tracer to actually get stored in project files.
  • A bug that caused the Spider not to honor the "Maximum parameterized requests per URL" setting.
  • A bug that caused some lightweight popups to have full window decoration on some Linux desktop managers.
  • A bug that incorrectly handled loading of IP addresses from file into the scope configuration UI.
  • A bug that prevented upstream SNI from working when proxying traffic through Burp from an Android emulator.
  • A bug that caused report generation to fail altogether when it encountered an incomplete issue due to project file corruption.
MD5: 99e7126d8fd9c56a78e8a3464612e3c7
SHA256: be1b9c4c6c4d25a3d11bbd3ffff845a9ed3b2a1e7740c72ab89a913283eaad86

MD5: f48beee2667ec767ba733026e23043ce
SHA256: eb215ee1a453634685d5ec302ccd9c07031869ca72c9f2cce10cc8dd6c9989a2

MD5: b55145e3a432e78210a27f8cb8228bc3
SHA256: c7850eabdbacee1fc2e40b93d4f25503cbfab4c3a636063bb0f18325bbff1654

MD5: 92ad1d2b3166450d26601180793e65bd
SHA256: c07203e145fc475c80edb3fdf534e9880cc223d3f7ba581452f832b5bd7325d5

MD5: 2c458b547ca73c8912390a606722ee95
SHA256: 217596f1d59e6e535227b7837fc2126e948fc6eefe1bf5b470fd90a7a3592bca
MD5: 7543adff4ae24f7e9a32742232eb4443
SHA256: d73d89f51fa61085788f095f7177d26b930066cf57422ab18657191354111f75

MD5: ec600536f24455f8ad8f20c3e600ffbb
SHA256: df5fdd580ba1bc777d0ffa9a79e66a5171fce879af04d74d54ce9b9c884b559e

MD5: f579b2b8692dde5d0ef6388d91a98d55
SHA256: 9f5fcc2d0a10e00ef67632f49a12499fcd1730d738c67b9c323e2a7f0c345ab9

MD5: 54cbe4b8ae891a125a661d8c26b17181
SHA256: 3131d6b62dc6f43f306442327d3b3cecd0ef75897fc553c9a1a66629ceef982e

MD5: 562fe599a8e3586f29c0e8cad2e41498
SHA256: ca3f2b2929d8eb048e1f9a0f9103105cd032edbbe94b110420d9ce1d6495f09f

Thursday, August 3, 2017


This release adds a number of new scan checks relating to file upload functionality.

Burp Scanner has always treated the contents of a file upload (within a multipart POST request) as a regular insertion point where payloads can be placed. In the new release, various additional checks are performed on the file upload:
  • Some new payloads are used to upload files in various formats, such as PDF, SVG, HTML, PHP, and SSI.
  • Where relevant, Burp now modifies the file extension and content-type fields in the upload request to reflect the type of file that is being uploaded, so as to maximize the chance that the application will handle the file in the desired way.
  • Both in-band and out-of-band techniques are used to detect vulnerabilities in the application's handling of uploaded files.
For example, Burp can now detect server-side rendering of uploaded PDF documents, by using some embedded PDF JavaScript to trigger a Burp Collaborator interaction when the document is rendered:

The new detection techniques all lead to new versions of existing issues, notably PHP code injection, SSI injection, reflected XSS, stored XSS, and external service interaction.

Note: Some updates have been made to Burp Collaborator server to support the new scan checks. People running private Collaborator servers should update these now. As usual, Burp will show an alert on startup if the configured Collaborator server is out of date, and you can use the Collaborator health check to determine this at any time.

A number of bugs are also fixed, including a recently introduced bug affecting NTLM authentication.
MD5: a7b86742d1b7e63f56a7f0d713eea4de
SHA256: 4ad9c1a01f9428b77a5af70d0f2035029af1cf6cf28aed44493cb9848926dc32

MD5: d046d7cf3892a4c67b68a29e4af33c66
SHA256: 859b1625e411c58b6b6d64f8e7516bc74449849ceddc082622f8cfa4ddffe36d

MD5: 1ce58a5dc102f013b197972e023f2bd8
SHA256: da3f6386339d1ef3966f8c5598d9b6259d85e4b5ae99fce795198bd73bcfadd4

MD5: d3ab9ced8c2be6ff7d63b1dc4238685c
SHA256: dc29bc8850962fdb7ca0278e9b16a24e3fb3f500fc7405970b576ea5f8247588

MD5: 8c4873f0d7b81919b07cdc62822204a9
SHA256: 9424941730379d394fa8fe6df2dc1393c13df12fdf0fcab484ebadb1ecc75c6a
MD5: 495c3c1de6f8d4ba9b1eb44eadf28e9a
SHA256: c3b4eed80b6ec52e40ef973235fde22aa752f7a3e52e3c5238271c9cf15631da

MD5: bd22ac1d8eb6fbefda3397f87882ad83
SHA256: f85687cf68b8d9cac45fd3eca9eabadf710aa711dc3253abb6f05a3d681327fc

MD5: 5d1cbbebc7fb59a399ae7bcacbe05f74
SHA256: eb3edd7bde5b335ac463136a5b0ce54f5e9dd8971a25fc73477384f5e0ae3b1a

MD5: 89db4bc21a2b6857add677a7184f4e91
SHA256: 48a87db46976e7a8d0eb5668a0d18d42939f812b8830c754b5d59275ad001121

MD5: b208bbe5d46048c914f93791c4432530
SHA256: e42bd27853fc59de5e645e7868b66a82eadef89c1ec7a504b5d8083536973d5b

Thursday, July 27, 2017


This release adds a number of new scan checks based on our talk today at Black Hat, Cracking the lens: targeting HTTP's hidden attack surface.

The new scan checks use various techniques aimed at inducing vulnerable applications and infrastructure to route requests to a different destination. This can lead to serious attacks, for example SSRF against the application server itself or other infrastructure components. The research behind the new capabilities quickly netted us over $30,000 in bug bounty payouts, and demonstrates the huge power of OAST (out-of-band application security testing).

The novelty of the new checks lies not so much in the payloads themselves as where they are placed. The new scan checks send Collaborator-based payloads in the following locations:
  • The HTTP Request-Line (where the requested URL normally appears).
  • The server name specified in the SSL SNI extension.
  • The server specified in a CONNECT request.
  • The Host header.
  • Various other common and not-so-common request headers.
An example of a reported vulnerability is shown below. For full details of these and various other techniques, see today's blog post.
MD5: f66087ddd397d3b293468d308c512882
SHA256: 86a601aa79d8ef7353b5553cf72f32923ce6a1c9824c570bdc55734960c2ebf4

MD5: 7d4d7ce37c03198db796b8ce2e33ff68
SHA256: bd1153672fab9250e3ab313f239948f37271f45d63c30b02a41cf2652f735c88

MD5: 6995f2f0a24b014a6708f42657be7086
SHA256: e3df386479dac58a27ff436ee2a9508f0c66c8c3053b40b38f524104b9ba2990

MD5: 7a04f8454ba3d34299748c18184da08f
SHA256: c4290923b9e77db55b436e0d2f932277aa97d7dace56b3464f1ec515670d0e5d

MD5: 07dad6f191ee8335c1d5e131102e9dc7
SHA256: ebfd26f0396a1c38826b83ad98e3242f7a2964bf85aa7acb886f73278921eb39

Tuesday, July 18, 2017


This release adds a new feature to save a copy of the current project.

You can choose the tools whose data you want to be included in the project file and whether you only want to save in-scope items.

The new feature is useful for various purposes:
  • You can begin working in a temporary project, and later save it to disk if it proves useful.
  • You can save a live backup copy of a disk-based project while continuing to work.
  • You can save a smaller copy of a project after refining your target scope or deleting unnecessary data.
Note that after Burp saves the copy of the current project, it continues working in the current project. If you want to switch to using the newly saved copy, you will need to restart Burp and select the new project file at startup.

Some bugs have also been fixed:
  • A bug that caused SNI not to work with upstream HTTP proxy servers.
  • A bug that caused the Burp Infiltrator patcher to cause bytecode corruption, or fail to patch at all, when certain unusual bytecode features were encountered.
  • A bug that could cause remembered user settings to be lost if the user closed down Burp during startup.
  • Various other bugfixes and enhancements.
MD5: 5ca9ba7734ee97fbb8b1bd2343e94b72
SHA256: 37130dbff32c552c5ac20e2855515217ffc1e7285aae6d12f862d026b3365896

MD5: 5b9a650f0eeda7d5a477836f8e768a91
SHA256: 4edfbf71499ffbaa5baaac04db6eed995537ca39da98928e649e6922abff1f20

MD5: c9d2945ce3da7d6965745128c96ae5d9
SHA256: 265642d84921be9298a979fc963382e845c629c2effa76827ca54394a447f8ac

MD5: 1fcccd74d654c28356479cb2c99528e4
SHA256: 68ac0a547eaef6d2b3b80ef957022270dcce98452fec42795489b4cc00313042

MD5: c93e28ea48cad1df0171284a02be8086
SHA256: 005d16f08047062fb6bdee6deabbbf13eee63d14188d8acfa073ffd8cb032db7
MD5: 255fc4175b53f354f1c871ff96d49cdf
SHA256: e468618b8d06ac3b661a1df49aa2505a47f2d12e36edbddcab3dab9683422a01

MD5: c75615e238d49c63a1443692d25ddd18
SHA256: 4704416581977d01c3da66c5d3450e0ec1d7366ef871ddae49df17039357d173

MD5: 0c88ca1dccbb70e40ee5484a9ba36879
SHA256: e47eb6be8a54684623a8494cbffac4ced49f3228f3ad1c898e7bf54ff671b550

MD5: 3b6e9252deb81ddb44412c119271ad64
SHA256: d49f840c3d820175907a56033432f230ca392e4aad2ff01fc70418d5a1dd764e

MD5: f65275ba3316348079b95c032195db17
SHA256: d60550e64089dda0e5e786d80f8fc9862be4de2b8f5397fdbe7e48f8d310e0dd