Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

[Vulnerability] Repeating patterns in encrypted files #4

Open
TypicalHog opened this issue Jun 9, 2018 · 1 comment
Open

[Vulnerability] Repeating patterns in encrypted files #4

TypicalHog opened this issue Jun 9, 2018 · 1 comment

Comments

@TypicalHog
Copy link
Owner

When the file is split into 256-byte blocks attacker can identify the blocks or parts of blocks that contain the same data (but not the data itself). Every individual byte with the same value and the same relative position in the block will always encrypt to the same output value, attacker will encounter false positives but this could still be very helpful to them.

Example with 4-byte blocks:

AAAAABCDGFGAAAAA -> FABDFCCEABADFABD (it might look random at first glance, but it's not)

Input:  [(A)AA(A)] (A)BCD GFG(A) [AAAA]
Output: [(F)AB(D)] (F)CCE ABB(D) [FABD]

This will be fixed in the future release.

@TypicalHog TypicalHog self-assigned this Jun 9, 2018
@TypicalHog TypicalHog changed the title [Vulnerability] Repeating patterns within 256-byte blocks [Vulnerability] Repeating patterns within the encrypted file Jun 9, 2018
@TypicalHog TypicalHog changed the title [Vulnerability] Repeating patterns within the encrypted file [Vulnerability] Repeating patterns in the encrypted file Jun 9, 2018
@TypicalHog TypicalHog changed the title [Vulnerability] Repeating patterns in the encrypted file [Vulnerability] Repeating patterns in encrypted files Jun 10, 2018
@TypicalHog
Copy link
Owner Author

This can be fixed by chaining the blocks together or by encrypting the key with itself after each 256-byte chunk of plaintext.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant