Re:Hijacking user sessions with the Heartbleed vulnerability
by smtddr on Tuesday April 08, 2014 @02:41PM
(#7555156)
For those that don't python and/or don't know where to edit.
hb = h2bin('''
18 03 02 00 03
01 40 00
''')
See that "40 00" there? That's hex and 0x4000 = 16384. Change it to something like "02 00", so it's 0x200 = 512, or 0x400 = 1024 ...or whatever you want.(But keep it at a power of 2... I assume).
Re:Hijacking user sessions with the Heartbleed vulnerability
by axisK on Tuesday April 08, 2014 @04:54PM
(#7555937)
As long as it's valid hex it should be fine, there seems to be a lower bound at which point servers don't respond but I didn't play around for too long with that part.
Most articles also mention 64kb which the script can do with some small modifications.
Re:Hijacking user sessions with the Heartbleed vulnerability
by 2bjorn on Sunday April 13, 2014 @08:16AM
(#7581087)
you might also want to use [1]
xmpp, starttls, proxy support with valid tls records, custom palyoad and stuff.. configurable via cmdline options.
[1] https://gist.github.com/tintinweb/10411753 | hb-test.py aka heartbleed.py
EDIT: The other thing is that it seems better to check for "Server Hello Done" at the end of the handshake message as some servers seem to send all submessages within one handshake message (though not sure if they're OpenSSL-based), i.e. look for ord(pay[-4]) == 0x0E rather than at ord(pay[0]).