Bitflip effect on encryption operation modes
In a bitflip attack, the attacker modifies ciphertext in a way that predictably changes the decryption result. This way, an attacker can tamper with data even if it’s encrypted. How this works depends on which encryption mode of operation is used. In this post we’ll look into what behavior each mode has when a bit is flipped.
Bit flipping
Block ciphers can only encrypt fixed-size blocks, typically of 16 bytes in length. These ciphers themselves are secure against bit flipping: if the input is changed slightly, the output changes significantly. Bit flipping becomes possible if several ciphertext blocks are combined in a certain way. In several modes of operation the ciphertext is XORed with plaintext from the next or previous block. This means that flipping a bit garbles one whole block, and flips one bit in another block.
CBC example
For a practical example, consider we are served an encrypted cookie that contains the following:
{"user": "johndoe", "nick": "john", "admin": 0}
When this is encrypted using CBC mode, it is split up in blocks of 16 bytes. Each block is XORed with the previous block (or the initialization vector) and encrypted. The message consists of the following blocks:
{"user": "johndo
e", "nick": "joh
n", "admin": 0}
The attack
In our bitflip attack, we flip a bit in the ciphertext of block 2. This will cause block 2 in the decrypted plaintext to become garbage, but it will also flip a bit in block 3. This happens because the decryption result is XORed with the ciphertext of the previous block, which is under our control:
The result is a cookie with the admin flag set to 1:
{"user": "johndoaRbUTPasBIrmAnO5n", "admin": 1}
In this example the result looks like valid JSON, which is required if we want to trick the application to think we are an administrator. This is because we conveniently assumed that the decryption only results in ASCII characters. In reality, the decryption will yield binary and it depends on how the application handles this whether a bitflip attack is feasible.
Block cipher modes of operation
Various modes combine the blocks in various ways. This means that the behavior of a bitflip attack differs for each mode. Here is the summary:
- EBC: garbles same block
- CBC: garbles same block, flips bit in next block
- PCBC: garbles same and all following blocks
- CFB: flips bit in same block, garbles next block
- OFB: flips bit in same block
- CTR: flips bit in same block
Try it
The form on bitflip.php makes use of unauthenticated encryption. If you fill out the form it redirects you to the page with encrypted data in the URL. See if you can modify the encrypted data in such as way that you become administrator.
Some hints:
- The form values are converted to JSON, encrypted and encoded as hexadecimal.
- The JSON contains
"is_admin": 0
. The goal is to change this to"is_admin": 1
, or any other value. - You can change the length of the input to get the data you want to modify in a certain block.
Conclusion
If data is encrypted this does not mean that an attacker can’t tamper with it. By flipping a bit in the ciphertext it is possible to determine which block mode is used, as long as the application reflects a bit of plaintext.