login

Burp Suite, the leading toolkit for web application security testing

Burp Suite Professional - Release Notes

Monday, July 28, 2014

v1.6.03

This release includes a new engine for static analysis of JavaScript code. This enables Burp Scanner to report a range of new vulnerabilities, including:
  • DOM-based XSS
  • JavaScript injection
  • Client-side SQL injection
  • WebSocket hijacking
  • Local file path manipulation
  • DOM-based open redirection
  • Cookie manipulation
  • Ajax request header manipulation
  • DOM-based denial of service
  • Web message manipulation
  • HTML5 storage manipulation
For more details, see the blog post.

MD5: bacd658a929c4a69580ea646d03b7d03
SHA256: 8f4ed620356d2ecedd3a8be6754137e0788dc3e1b6e2df628a28f1a8a75a21a7

Tuesday, July 22, 2014

v1.6.02

This release contains various bugfixes and minor enhancements:
  • A bug that caused certain HTML content to be wrongly inferred as JavaScript, with a knock-on effect on the Scanner's XSS checking logic, has been fixed.
  • A bug introduced in v1.6.01 affecting the passing through of command line arguments to extensions has been fixed.
  • A bug that sometimes caused session handling rules using macros to be incorrectly restored from state files, has been fixed
  • A bug that occasionally caused corruption in the rendering of live streaming responses has been fixed.
  • A bug where the "time of day" value in Intruder attack results was incorrectly reported when request throttling was enabled, has been fixed.
  • Logging options have been enabled for the Sequencer tool.
  • Links in the BApp details tab are now clickable and open in an external browser.
  • Renamable tab captions now prevent accidental renaming to an empty string, which previously resulted in a pixel-perfect double-click being required to rename the tab to anything else.
  • Efforts have been made to fix an occasional bug that causes the UI to freeze when changing the confidence or severity of Scanner issues. Feedback is welcomed on whether this bug has indeed gone away.
MD5: e9a5a822c3075f827b9c953d9c52336c
SHA256: ae0c91a1768f4b5c9b1585bad05dbb18e160978f42976ac720a666d2d5fcc982

Wednesday, June 11, 2014

v1.6.01

This release contains various enhancements to existing functionality:
  • The Spider's link-discovery engine has been enhanced, and now achieves a WIVET score of 50%. There is more work to do in this area, and improved crawling of JavaScript-driven navigation is in the pipeline.
  • There are new hotkeyable actions to go back and forwards in the Repeater history for the currently displayed tab. Hotkeys can be assigned to these actions at Options / Misc / Hotkeys.
  • The "valid from" time on Proxy-generated CA-signed host certificates has been changed to be 30 days in the past, to reduce problems that can arise when using multiple test machines with different system times.
  • Handling of non-HTTP-compliant messages that use \n instead of \r\n as header delimiters has been improved.
  • A new option has been added to prevent access to the in-browser Proxy interface using a fully-qualified DNS name, to hinder DNS rebinding attacks against it.
Various bugs have been fixed, including:
    • A bug that resulted in a cryptic error message when attempting to restore state from an invalid file that wasn't generated by Burp's save state function.
    • A bug in the Proxy's generation of CA-signed host certificates when the Proxy listener is configured to do host redirection. Previously, the certificate was being generated for the redirected hostname, not the original one requested by the browser, causing a certificate error in the browser.
    • A bug in the Proxy's match/replace function where replacement strings containing regex metacharacters are wrongly handled when doing non-regex-based match/replace.
    • A bug where target host redirection performed by a Burp extension (by modifying the target details for the current request) is not honored when using SSL with an upstream proxy server. Previously, Burp made a CONNECT request using the original hostname, not the modified one.
    • A bug which caused some session handling rules to fail when processing multipart requests containing a file upload parameter.
    MD5: 23f5392b6dc4a41f19c4afc619e8fc3f
    SHA256: acdcf6f40a1152dd72a198869b99d3c6ec82fa9a7281e3d2454e0d475b62c2d5

    Tuesday, April 15, 2014

    v1.6

    This is the final v1.6 release.

    Burp Suite Free Edition contains significant new features added since v1.5, including:
    • Support for WebSockets messages.
    • Support for PKCS#11 client SSL certificates contained in smart cards and physical tokens.
    • A new Extender tool, allowing dynamic loading and unloading of multiple extensions.
    • A new powerful extensibility API, enabling extensions to customize Burp's behavior in much more powerful ways.
    • Support for extensions written in Python and Ruby.
    • A new BApp Store feature, allowing quick and easy installation of extensions written by other Burp users.
    • An option to resolve DNS queries over a configured SOCKS proxy, allowing access to TOR hidden services.
    • Generation of CSRF PoC attacks using a new cross-domain XHR technique.
    • New options for SSL configuration, to help work around common problems.
    • Optional unpacking of compressed request bodies in the Proxy.
    • Support for .NET DeflateStream compression.
    • New and improved types of Intruder payloads.
    • New Proxy interception rules.
    • New Proxy match/replace rules.
    • Improved layout options in the Repeater UI.
    • An SSL pass-through feature, to prevent Burp from breaking the SSL tunnel for specified domains.
    • Support for the Firefox Plug-n-hack extension.
    • An option to copy a selected request as a curl command.
    Burp Suite Professional contains a number of bugfixes and tweaks, added since the last beta version, including:
    • An occasional bug causing misplaced highlights on payloads in Scanner issues has been fixed.
    • A bug in which restoring default settings for the Extender tool didn't unload any currently running extensions has been fixed.
    • A display bug affecting the rendering of binary content (such as images) in the raw view of the HTTP message editor has been fixed.
    • A bug which prevented the automatic backup on exit feature from functioning in headless mode has been fixed.
    • In previous versions, Burp stored its preferences in separate locations for each major version. This caused persisted settings to be lost on upgrading to a new major version. This behavior has been modified, and from v1.6 onwards major versions will store their preferences in the same location. As a workaround to preserve settings from earlier releases, Pro users can launch the earlier release, save a state file containing their preferences, then launch the new release and load the state file.
    Work is already underway on some exciting new features that will be arriving post v1.6 ...

    Free edition
    MD5: 6f2c0ff4e3cab35bb49312ce88e1a690
    SHA256: 21cfdd2d2f682997648f3877bca239bde358f8ce5a2a9304fd1de72fc68a3312

    Pro edition
    MD5: 8d56e783e79f615feefd3717322d61dd
    SHA256: d81a765df2eb2fc33f91cdbf2669264204a9acf2ed7e43187ff7632015ffa89b

    Thursday, April 3, 2014

    v1.6beta2

    This release fixes a number of bugs:
    • A bug in v1.6beta that caused some saved state files to be corrupted has been fixed. The majority of problematic state files that were generated with the previous version should be loadable in this release.
    • A bug in the HTTP message viewer which caused parts of a message not to be displayed in certain situations has been fixed.
    • A bug arising on certain platforms (e.g. some OS X retina machines), in which the HTTP message viewer displays the cursor in the wrong position, has been addressed. Since this was a platform-specific problem, and we weren't able to reproduce the bug on all reported configurations, we welcome feedback as to whether any further instances of this problem are remaining.
    • Problems affecting Proxy SSL negotiation on Java 8 have been addressed. Burp is not yet officially supported on this platform, pending further testing, but we welcome feedback about any further problems that arise on Java 8.
    • Some XSS edge cases relating to URL-encoding of specific payload characters, which were being missed by Burp, are now detected properly.
    • A bug in the Intruder custom iterator payload type, which caused it not to generate the expected payloads in certain conditions, has been fixed.
    • The opt-out checkbox for reporting of anonymous performance feedback, which previously appeared only on an options panel, has been added to the EULA acceptance dialog.
    MD5: 2bae268d34ead1cf4cecc8a31840a427
    SHA256: 8d3c71c4044f039e87f0838335e698d29d68e00dfe76c3a987eec93f138456d0

    Tuesday, March 4, 2014

    v1.6beta

    This release introduces the BApp Store, a repository of Burp extensions that have been written by users of Burp Suite, to extend its capabilities:


    You can install BApps with one click from within Burp, and you can also download them from the BApp Store web site for manual installation on machines without Internet access. We've assembled an initial list of extensions and will hopefully be adding more soon.

    The handling of URL-encoding of parameters within session handling macros has been rationalized, to make Burp "just do" the right thing in nearly every case, without the need for any special configuration by the user. Previously, there was a per-parameter configuration option whether to URL-encode its value. Since Burp actually knows the context in a response from which a parameter's value is being derived, and the context in a subsequent request into which it is being placed, Burp can automatically take care of the encoding in exactly the cases where it is needed.

    The exception to this, where some manual configuration is still required, is where you have configured a custom parameter location within a response. Since this is a custom location, you need to tell Burp whether or not the raw extracted value is already URL-encoded, and Burp will handle it correctly when using its value in subsequent requests.

    A bug that was introduced in v1.5.21, affecting Proxy SSL negotiation in cases where the client has only specified an IP address, has been fixed. The previous behavior, where Burp fetches the authentic SSL certificate from the destination host and forges a copy signed by its own CA certificate, has been restored. This technique is necessary to support Android clients, which only send a target's IP address in the CONNECT request that precedes the SSL negotiation.

    This is officially a beta release, and when the final version is released, relevant changes since v1.5 will be ported into a new release of Burp Suite Free Edition.

    MD5: 06c8148609ff9f9ad9f92937c2047425
    SHA256: 7f4b26e428742b00a8464150ef82a2c94720ef9b62ea513435f41bf4dfb39265

    Thursday, January 30, 2014

    v1.5.21

    This release adds support for WebSockets to the Proxy tool. You can now view, intercept and modify WebSockets messages in the same way as regular HTTP messages:


    There is a new Proxy history tab for WebSockets messages, with the same capabilities as the HTTP history (filter, sort, search, etc.):


    You can configure whether incoming and outgoing WebSockets messages are intercepted at Proxy / Options / Intercept WebSockets Messages.

    The Scanner's support for nested insertion points, which was introduced in the previous release, has been updated:
    • Nested data in URL-encoded query string format is now recognized, and insertion points are created for each parameter value within the nested data. This is only done if the nested query string contains at least two parameters, so as to avoid false positive in common cases where a parameter value happens to contain the = character.
    • Highlighting of relevant syntax in reported Scanner issues is now fully precise within nested insertion points, and picks out the exact item of input that Burp modified in order to identify the issue.
    The Scanner reporting function now has an option to embed report images inline within the generated HTML. This works on all recent browsers, but you can revert to the old behavior (of images stored in a subdirectory) if you prefer.

    There is a new function to report anonymous feedback about Burp's performance. This will help us improve Burp by obtaining technical information about problems within Burp. The feedback does not identify the user, but you can turn this function off at Options / Misc / Performance Feedback.

    Various bugs have been fixed.

    MD5: b80c61d45054e483870f75fff35d0c56
    SHA256: 52903a758d6714aedb90a45f58a477df40288be76ae0f1961510c8755a4ef903

    Friday, November 29, 2013

    v1.5.20

    This release adds support for nested insertion points to the Scanner.

    Nested insertion points are used when an insertion point's base value contains data in a recognized format. For example, a URL parameter might contain Base64-encoded data, and the decoded value might in turn contain JSON or XML data. With the option to use nested insertion points enabled, Burp will create suitable insertion points for each separate item of input at each level of nesting.

    Below are some examples of Burp's new capabilities in scanning nested insertion points, running against some targets in our lab.

    SQL injection into a Base64-encoded value within a JSON value within a URL parameter:



    SQL injection into a JSON value within XML within a URL parameter:



    SQL injection into XML within a JSON value within a URL parameter:



    XSS in a JSON value within a Base64-encoded URL parameter:



    XSS in a JSON value within XML within a URL parameter:



    XSS in an XML value within JSON within a URL parameter



    You get the idea. There is no limit to how deep Burp can go. If it recognizes the data format of the base value of any insertion point, Burp will look inside that data for nested values that should be tested.

    The option to include nested insertion points is on by default, and using this option imposes no overhead when scanning requests containing only conventional parameters. However, it enables Burp to reach much more of the attack surface of today's complex applications where data is encapsulated within different formats.

    MD5: 08396c07da2f11a9f17212c3e4299b07
    SHA256: d4e547b8d1bd63d2b65b605239c9c03058080deed14e3bfe9ebe538601baf537

    Monday, November 25, 2013

    v1.5.19

    This release contains a number of enhancements to the Scanner tool.

    Active Scanner optimization

    There is a new set of Scanner options which let you control the behavior of the active scanning logic in relation to scan speed and accuracy:


    • Scan speed - This option determines how thorough certain scan checks will be when checking for vulnerabilities. The "Fast" setting makes fewer requests, and checks for fewer derivations of some vulnerabilities. The "Thorough" setting makes many more requests and checks for more derivative types of vulnerabilities. The "Normal" setting is mid-way between the two, and represents a suitable trade-off between speed and thoroughness for many applications.
    • Scan accuracy - This option determines the amount of evidence that the Scanner will require before reporting certain types of vulnerabilities. Some issues can only be detected using "blind" techniques, in which Burp infers the probable existence of a vulnerability based on some observed behavior, such as a time delay or a differential response. Because these observed behaviors can occur anyway, in the absence of the associated vulnerability, the techniques are inherently more prone to false positives than other techniques, such as the observation of error messages. To attempt to reduce false positives, Burp repeats certain tests a number of times when a putative issue is inferred, to try and establish a reliable correlation between submitted inputs and observed behaviors. The accuracy option is used to control how many times Burp will retry these tests. The "Minimize false negatives" setting performs fewer retries, and so is more likely to report false positive issues, but is also less likely to miss genuine issues due to inconsistent application behavior. The "Minimize false positives" setting performs many more retries, and so is less likely to report false positive issues, but may as a result wrongly miss some genuine issues, because some of the retry requests might just happen to fail to return the result being tested for. The "Normal" setting is mid-way between the two, and represents a suitable trade-off between false positive and false negative issues for many applications.

    Payload encoding

    Burp's internal logic handling the placement of scan payloads into insertion points has been reworked to resolve some occasional problems. In previous versions, Burp applied incorrect encoding to certain payloads in certain insertion points - for example, wrongly URL-encoding some characters in locations where URL-encoding is not necessary. This caused Burp to miss some edge case vulnerabilities in applications where Burp's non-standard encoding was not tolerated.

    The improved handling of encoding within insertion points paves the way for some further enhancements to the Scanner's capabilities, and the next Scanner update will include more more powerful insertion point types, enabling Burp to find more vulnerabilities in today's complex applications.

    Extensions

    In order to fix the erroneous handling of encoding within some insertion points, Burp's contract with extensions in relation to customizing the Scanner has unfortunately needed to change. We apologize for this, however the previous contract was in any case not consistent, and left extensions with impossible responsibilities in some situations.

    Previously, Burp-provided insertion points did not do any payload encoding, and extension-provided checks were required to submit suitably encoded payloads based on the insertion point type (for example, URL-encoding spaces in URL parameters, HTML-encoding tag brackets in XML parameters, etc.). In some cases, it wasn't actually possible for extensions to fully determine the encoding that was needed. Further, the old approach risked leaving extensions unable to deal with new insertion point types that we plan to introduce to Burp. In the new contract, Burp-provided insertion points will automatically carry out suitable encoding of payloads, and so extension-provided checks should submit raw payloads.

    Regarding extension-provided insertion points, the contract has always been that Burp will submit raw payloads (although this contract may have been inconsistently honored by Burp due to the payload encoding issues described in the previous section). This contract remains in place and is now strictly followed by Burp, so extension-provided insertion points need to handle encoding of relevant payload characters based on the nature of the insertion point.

    This change in the contract brings consistency to the responsibility of Burp- and extension-provided insertion points, and enables both Burp and extensions to function in a less coupled, more future-proof way.

    Note that in a few rare cases, an extension-provided check may require complete control over how its payloads are encoded within insertion points - for example, in order to violate protocol-level rules for the proper representation of data in different contexts. In this situation, the extension should also create its own custom insertion points, in order to gain full control over the end-to-end payload handling process.

    In addition to the previous changes, as an aid to extension authors, Burp's implementation of IScannerInsertionPoint.buildRequest() has been modified so that Burp always fixes the Content-Length header when the message body length has changed. Extension-provided implementations of this method are not obliged to do this.

    XML reporting

    The XML-based reporting of Scanner issues now includes the following details:
    • method attribute on request elements, indicating the HTTP method used in the request.
    • A collection of issueDetailItem elements on some issue types, such as disclosure of email or IP addresses, containing the individual information items in machine-readable form.

    User interface

    In Scanner options, the panels with checkboxes to enable specific active and passive checks now have "Select all" and "Select none" buttons.

    The Scanner reporting wizard, the panel with checkboxes to select specific types of issue to report now has "Select all" and "Select none" buttons.

    MD5: 2219c127beef63a7c687dad1ba723e8c
    SHA256: 432fe093ac09839bc4365e34015a8a7bdbd0583e26099582ca66b627e66baf98

    Thursday, November 7, 2013

    v1.5.18

    This release includes a number of updates to the Scanner tool:
    • Several checks for new types of vulnerabilities have been added.
    • Various existing checks have been enhanced to improve their accuracy in avoiding false negatives and positives.
    • A number of bugs have been fixed.
    The new types of issues that Burp can now report are:
    • Remote file inclusion
    • Recursive XML entity expansion
    • Response dependent on X-Forwarded-For header in request
    • "Long" redirection responses
    • Base64-encoded data within request parameters
    MD5: b31353680bd08568fdc0fce15fedec13
    SHA256 : 40b917c1a9034ec0c0698968c2bbbcde2e07a842043015843a30fcdd11f31b5d


    User Forum

    Get help from other users, at the Burp Suite User Forum:

    Visit the forum ›

    Copyright 2014 PortSwigger Ltd. All rights reserved.