Closed GoogleCodeExporter closed 9 years ago
Same on Backtrack 5 r2, Reaver 1.3 r65
Original comment by patricks...@gmail.com
on 5 Jan 2012 at 1:03
[deleted comment]
I'm not getting this error with the SVN code, I'll try to reproduce with the
1.3 release; can either of you provide gdb output or a pcap that can be used to
replicate the bug?
Original comment by cheff...@tacnetsol.com
on 5 Jan 2012 at 4:53
I will wait for reaver 1.4 may bee i made the mistake, after the 3rd start of
walsh it does not exit with this buffer overflow.
Original comment by patricks...@gmail.com
on 5 Jan 2012 at 6:07
Buffer overflows are never a user mistake, always a developer mistake. I will
try to reproduce the problem on my end; if this happens again, please let me
know.
Original comment by cheff...@tacnetsol.com
on 5 Jan 2012 at 6:14
I apologize for my bad English. After compilation, I did "make install" so it
did not create the /etc/reaver/reaver.db. After creating without error, no
buffer overflow. Output from gdb will supply later.
Original comment by mmare...@gmail.com
on 6 Jan 2012 at 8:10
For debugging purpose
Original comment by maxmust...@gmail.com
on 7 Jan 2012 at 9:08
Attachments:
Thanks for the pcap, I can now reproduce the bug here.
Original comment by cheff...@tacnetsol.com
on 9 Jan 2012 at 3:56
Found the bug in the parse_beacon_tags function; pcap helped a lot, thanks
much. Fix has been checked in.
FYI, there appears to be a lot of corrupted data in the captures you are
getting.
Original comment by cheff...@tacnetsol.com
on 9 Jan 2012 at 4:47
Thanks. Good job.
Original comment by mmare...@gmail.com
on 9 Jan 2012 at 7:28
Original issue reported on code.google.com by
mmare...@gmail.com
on 5 Jan 2012 at 1:00