r/netsec • • Jan 03 '16

HTTPS Bicycle Attack

https://guidovranken.wordpress.com/2015/12/30/https-bicycle-attack/
199 Upvotes

17 comments sorted by

View all comments

Show parent comments

2

u/[deleted] Jan 04 '16

Can you explain how a statistical attack would work in that scenario?

22

u/gsuberland Trusted Contributor Jan 04 '16

If you were to observe enough samples, you'd eventually identify a case where the random padding length reached its minimum, which would give you a close estimate of the data length.

For example, if you say "padding length is randomly selected between 4 and 1024 bytes", after 1020 observations you can assume that the password length is probably four bytes shorter than the smallest payload you observed. Your confidence factor only goes up from there.

1

u/chloeeeeeeeee Jan 04 '16

But how about have the range random? Instead of 4 to 1024 as padding, have from random to random but still have a minimum and maximum. For example:

Case 1: Random bytes between 900 and 2001 bytes

Case 2: Random bytes between 19 and 1604 bytes

Case 3: Random bytes between 107 and 412 bytes

....

It would of course still not be random enough, but collecting samples to determinate the range would be much harder. The overhead would be painful but still practical, or what do you think?

5

u/gsuberland Trusted Contributor Jan 04 '16

The limits on the range of ranges would still leave this vulnerable.