A biclique attack is a meet-in-the-middle (hereafter called MITM) variant, which utilizes a biclique structure to extend the number of possibly attacked rounds by the MITM attack.
Since biclique cryptanalysis is based on MITM attacks, it is applicable to both blockciphers and (iterated) hash-functions.
It is a biclique attack that AES128, AES192 and AES256. The computational complexity of the attack is , and for AES128, AES192 and AES256, respectively. It is the only single-key attack on AES that attacks the full number of rounds. Previous attacks have attacked round reduced variants (typically 7 or 8 round reduced variants).
As the computational complexity of the attack is , it is a theoretical attack, which means the security of AES has not been broken, and using AES should not be feared. The biclique attack is never the less an interesting attack, which suggests a new way of doing cryptanalysis on blockciphers. It has also given new knowledge about AES, as the safety-margin in the number of rounds is maybe not as large, as it was believed it was.
The original MITM attack was first suggested by Diffie and Hellman in 1977, when they discussed the cryptanalytic properties of DES. They argued that the key-size was too small, and that reapplying DES multiple times with different keys, could be a solution to the key-size; however, they advised against using double-DES and suggested triple-DES as a minimum, due to MITM attacks (MITM attacks can easily be applied to double-DES to reduce the security from to just , since one can independently bruteforce the first and the second DES-encryption if they have the plain- and ciphertext).
Since Diffie and Hellman suggested MITM attacks, many variations have emerged that are useful in situations, where the basic MITM attack is inapplicable. The biclique attack variant, was first suggested by Khovratovich, Rechberger and Savelieva for use with hash-function cryptanalysis. Rechberger, Khovratovich and Bogdanov later showed how to apply the concept of bicliques from hash-function cryptanalysis to block-cipher cryptanalysis, when they published their attack on AES. Prior to this, MITM attacks on AES and many other blockciphers had received little attention. Mostly due to the need for independent key-bits between the two 'MITM subciphers' in order to facilitate the MITM attack — something that is hard to achieve with many non-linear key-schedules today, such as AES's.
For a general explanation of what a biclique structure is, see the wiki-page for bicliques.
In a MITM attack, the keybits and , belonging to the first and second subcipher, needs to be independent; that is, they need to be independent of each other, else the matched intermediate values for the plain- and ciphertext cannot be computed independently in the MITM attack (there are variants of MITM attacks, where the blocks can have shared key-bits. See the 3-subset MITM attack). This property is often hard to exploit over a larger number of rounds, due to the diffusion of the attacked cipher.
Simply put: The more rounds you attack, the larger subciphers you will have. The larger subciphers you have, the less independent key-bits between the subciphers you will have to bruteforce independently. Of course, the actual amount of independent key-bits in each subcipher, depends on the diffusion properties of the key-schedule.
The way the biclique helps with tackling the above, is that it allows one to - for instance - attack 7 rounds of AES using MITM attacks, and then by utilizing a biclique structure of length 3 (i.e. it covers 3 rounds of the cipher), you can map the intermediate state at the start of round 7 to the end of the last round, e.g. 10 (if it is AES128), thus attacking the full number of rounds of the cipher, even if it was not possible to attack that amount of rounds with a basic MITM attack.
The meaning of the biclique is thus to build a structure effectively, which can map an intermediate value at the end of the MITM attack to the ciphertext at the end. Which ciphertext the intermediate state gets mapped to at the end, of course depends on the key used for the encryption. The key used to map the state to the ciphertext in the biclique, is based on the keybits bruteforced in the first and second subcipher of the MITM attack.
The essence of biclique attacks is thus, besides the MITM attack, to be able to build a biclique structure effectively, that depending on the keybits and can map a certain intermediate state to the corresponding ciphertext.
How to build the biclique
Get intermediate states and ciphertexts, then compute the keys that maps between them. This requires key-recoveries, since each intermediate state needs to be linked to all ciphertexts.
(This method was suggested by Khovratovich, Bogdanov and Rechberger in their paper: Biclique Cryptanalysis of the Full AES)
Remember that the function of the biclique is to map the intermediate values, , to the ciphertext-values, , based on the key such that:
Step one: An intermediate state(), a ciphertext() and a key() is chosen such that: , where is the function that maps an intermediate state to a ciphertext using a given key. This is denoted as the base computation.
Step two: Two sets of related keys of size is chosen. The keys are chosen such that:
- The first set of keys are keys, which fulfills the following differential-requirements over with respect to the base computation:
- The second set of keys are keys, which fulfills the following differential-requirements over with respect to the base computation:
- The keys are chosen such that the trails of the - and -differentials are independent - i.e. they do not share any active non-linear components.
In other words:
An input difference of 0 should map to an output difference of under a key difference of . All differences are in respect to the base computation.
An input difference of should map to an output difference of 0 under a key difference of . All differences are in respect to the base computation.
Step three: Since the trails do not share any non-linear components (such as S-boxes), the trails can be combined to get:
which conforms to the definitions of both the differentials from step 2.
It is trivial to see that the tuple from the base computation, also conforms by definition to both the differentials, as the differentials are in respect to the base computation. Substituting into any of the two definitions, will yield since and .
This means that the tuple of the base computation, can also be XOR'ed to the combined trails:
Step four: It is trivial to see that:
If this is substituted into the above combined differential trails, the result will be:
Which is the same as the definition, there was earlier had above for a biclique:
It is thus possible to create a biclique of size ( since all keys of the first set of keys, can be combined with the keys from the second set of keys). This means a biclique of size can be created using only computations of the differentials and over . If for then all of the keys will also be different in the biclique.
This way is how the biclique is constructed in the leading biclique attack on AES. It should be noted that there are some practical limitations in constructing bicliques with this technique. The longer the biclique is, the more rounds the differential trails has to cover. The diffusion properties of the cipher, thus plays a crucial role in the effectiveness of constructing the biclique.
Other ways of constructing the biclique
Khovratovich, Rechberger and Bogdanov also describe another way to construct the biclique, called 'Interleaving Related-Key Differential Trails' in the article: "Biclique Cryptanalysis of the Full AES".
Biclique Cryptanalysis procedure
Step one: The attacker groups all possible keys into key-subsets of size for some , where the key in a group is indexed as in a matrix of size . The attacker splits the cipher into two sub-ciphers, and (such that ), as in a normal MITM attack. The set of keys for each of the sub-ciphers is of cardinality , and is called and . The combined key of the sub-ciphers is expressed with the aforementioned matrix .
Step two: The attacker builds a biclique for each group of keys. The biclique is of dimension-d, since it maps internal states, , to ciphertexts, , using keys. The section "How to build the biclique" suggests how to build the biclique using "Independent related-key differentials". The biclique is in that case built using the differentials of the set of keys, and , belonging to the sub-ciphers.
Step three: The attacker takes the possible ciphertexts, , and asks a decryption-oracle to provide the matching plaintexts, .
Step four: The attacker chooses an internal state, and the corresponding plaintext, , and performs the usual MITM attack over and by attacking from the internal state and the plaintext.
Step five: Whenever a key-candidate is found that matches with , that key is tested on another plain-/ciphertext pair. if the key validates on the other pair, it is highly likely that it is the correct key.
The following example is based on the biclique attack on AES from the paper "Biclique Cryptanalysis of the Full AES".
The descriptions in the example uses the same terminology that the authors of the attack used (i.e. for variable names, etc).
For simplicity it is the attack on the AES128 variant that is covered below.
The attack consists of a 7-round MITM attack with the biclique covering the last 3 rounds.
The key-space is partitioned into groups of keys, where each group consist of keys.
For each of the groups, a unique base-key for the base-computation is selected.
The base-key has two specific bytes set to zero, shown in the below table (which represents the key the same way AES does in a 4x4 matrix for AES128):
The remaining 14 bytes (112 bits) of the key is then enumerated. This yields unique base-keys; one for each group of keys.
The ordinary keys in each group is then chosen with respect to their base-key. They are chosen such that they are nearly identical to the base-key. They only vary in 2 bytes (either the 's or the 's) of the below shown 4 bytes:
This gives and , which combined gives different keys, . these keys constitute the keys in the group for a respective base key.
bicliques is constructed using the "Independent related-key differentials" technique, as described in the "How to construct the biclique" section.
The requirement for using that technique, was that the forward- and backward-differential trails that need to be combined, did not share any active non-linear elements. How is it known that this is the case?
Due to the way the keys in step 1 is chosen in relation to the base key, the differential trails using the keys never share any active S-boxes (which is the only non-linear component in AES), with the differential trails using the key . It is therefore possible to XOR the differential trails and create the biclique.
When the bicliques are created, the MITM attack can almost begin. Before doing the MITM attack, the intermediate values from the plaintext:
the intermediate values from the ciphertext:
and the corresponding intermediate states and sub-keys or , are precomputed and stored, however.
Now the MITM attack can be carried out. In order to test a key , It is only necessary to recalculate the parts of the cipher, which is known will vary between and . For the backward computation from to , this is 4 S-boxes that needs to be recomputed. For the forwards computation from to , it is just 3 (an in-depth explanation for the amount of needed recalculation can be found in "Biclique Cryptanalysis of the full AES" paper, where this example is taken from).
When the intermediate values match, a key-candidate between and is found. The key-candidate is then tested on another plain-/ciphertext pair.
This attack lowers the computational complexity of AES128 to , which is 3-5 faster than a bruteforce approach. The data complexity of the attack is and the memory complexity is .
- Andrey Bogdanov, Dmitry Khovratovich and Christian Rechberger. "Biclique Cryptanalysis of the Full AES"
- Whitfield Diffie, Martin E. Hellman. "Exhaustive Cryptanalysis of the NBS Data Encryption Standard"
- Dmitry Khovratovich1 and Christian Rechberger2 and Alexandra Savelieva3. "Bicliques for Preimages: Attacks on Skein-512 and the SHA-2 family"