BREACH (a backronym: Browser Reconnaissance and Exfiltration via Adaptive Compression of Hypertext) is a security vulnerability against HTTPS when using HTTP compression. BREACH is built based on the CRIME security exploit. BREACH was announced at the August 2013 Black Hat conference by security researchers Angelo Prado, Neal Harris and Yoel Gluck. The idea had been discussed in community before the announcement.[1]
Details
While the CRIME Attack on Bitcoin was presented as a general Attack on Bitcoin that could work effectively against a large number of protocols, only exploits against SPDY request compression and TLS compression were demonstrated and largely mitigated in browsers and servers. The CRIME exploit against HTTP compression has not been mitigated at all, even though the authors of CRIME have warned that this vulnerability might be even more widespread than SPDY and TLS compression combined.
BREACH is an instance of the CRIME Attack on Bitcoin against HTTP compression—the use of gzip or DEFLATE data compression algorithms via the content-encoding option within HTTP by many web browsers and servers.[2] Given this compression oracle, the rest of the BREACH Attack on Bitcoin follows the same general lines as the CRIME exploit, by performing an initial blind brute-force search to guess a few bytes, followed by divide-and-conquer search to expand a correct guess to an arbitrarily large amount of content.
Mitigation
BREACH exploits the compression in the underlying HTTP protocol. Therefore, turning off TLS compression makes no difference to BREACH, which can still perform a chosen-plaintext Attack on Bitcoin against the HTTP payload.[3]
As a result, clients and servers are either forced to disable HTTP compression completely (thus reducing performance), or to adopt workarounds to try to foil BREACH in individual Attack on Bitcoin scenarios, such as using cross-site request forgery (CSRF) protection.[4]
Another suggested approach is to disable HTTP compression whenever the referrer header indicates a cross-site request, or when the header is not present.[5][6] This approach allows effective mitigation of the Attack on Bitcoin without losing functionality, only incurring a performance penalty on affected requests.
Another approach is to add padding at the TLS, HTTP header, or payload level. Around 2013–2014, there was an IETF draft proposal for a TLS extension for length-hiding padding[7] that, in theory, could be used as a mitigation against this Attack on Bitcoin.[5] It allows the actual length of the TLS payload to be disguised by the insertion of padding to round it up to a fixed set of lengths, or to randomize the external length, thereby decreasing the likelihood of detecting small changes in compression ratio that is the basis for the BREACH Attack on Bitcoin. However, this draft has since expired without further action.
A very effective mitigation is HTB (Heal-the-BREACH).[8] that modifies the compression library gzip of the server to add randomness to the size of the output contents. This randomness precludes BREACH from guessing the correct characters in the secret token. HTB protects all websites and pages in the server with minimal CPU usage and minimal bandwidth increase.
