Digital Repository

On Compression Ratio Info-leak Mass Exploitation (CRIME) Attack and Countermeasures.

Show simple item record

dc.contributor.author Prasadi, S.
dc.contributor.author Alupotha, J.
dc.contributor.author Fawzan, M.
dc.contributor.author Alawatugoda, J.
dc.contributor.author Ragel, R.
dc.date.accessioned 2017-09-12T08:50:49Z
dc.date.available 2017-09-12T08:50:49Z
dc.date.issued 2017
dc.identifier.citation Prasadi, S., Alupotha, J., Fawzan, M., Alawatugoda, J. and Ragel, R.2017. On Compression Ratio Info-leak Mass Exploitation (CRIME) Attack and Countermeasures.Kelaniya International Conference on Advances in Computing and Technology (KICACT - 2017), Faculty of Computing and Technology, University of Kelaniya, Sri Lanka. p 37. en_US
dc.identifier.uri http://repository.kln.ac.lk/handle/123456789/17407
dc.description.abstract Header compression is desirable for network applications, as it saves bandwidth. However, when data is compressed before being encrypted, the amount of compression leaks information about the amount of redundancy in the plaintext. This leads to the CRIME attack on web traffic protected by the SSL/TLS protocols. In order to mitigate the CRIME attack, compression is completely disabled in the TLS/SSL-layer. Although disabling compression completely mitigates the CRIME attack, it has a drastic impact on bandwidth usage. The attack is carried out with the assumption that the attacker has the ability to view the victim’s encrypted traffic. An attacker can accomplish this with a network protocol analyzer. It is also assumed that the attacker has the ability to make the victim client to send requests to the targeted web server. This can be accomplished by coercing the victim to visit an attacker-controlled site (which contains a JavaScript code that sends requests to the targeted server with attacker-injected values in request headers). The attacker will coerce the victim to send a small number of requests to guess the first byte of the secret cookie. The attacker then measures the size of the (compressed) request headers. With that information, the CRIME attack algorithm determines the correct value for the first character of the secret cookie. Since the attack relies on LZ77 loss-less data compression algorithm, the first byte of the target secret must be correctly guessed before the second byte is attempted. Separating secret cookies from compression is presented as a proven-secure countermeasure against CRIME attack in a previous work: (1)--separates all the secret cookies from the request header. (2)--rest of the header is compressed, while the secrets are kept uncompressed. Since the secret cookie is not compressed with the attacker-injected values, the origin of the compression leakage is shut. Thus, the proposed solution completely prevents the CRIME attack and also enables header compression. This is useful in reduction of network bandwidth usage. Figure 1 CRIME attack setup In this work we create a test environment to replicate the CRIME attack and to test countermeasures. en_US
dc.language.iso en en_US
dc.publisher Faculty of Computing and Technology, University of Kelaniya, Sri Lanka. en_US
dc.subject CRIME attack en_US
dc.subject SSL/TLS en_US
dc.subject Security cryptography en_US
dc.title On Compression Ratio Info-leak Mass Exploitation (CRIME) Attack and Countermeasures. en_US
dc.type Article en_US


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search Digital Repository


Browse

My Account