bugtraq - Re: Re: licq remote DoS?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: 10 Apr 2008 15:19:36 -0000
From: mrangelov@...bul.bg
To: bugtraq@...urityfocus.com
Subject: Re: Re: licq remote DoS?

You're right, there is no check against FD_SETSIZE. IMO it's a bad idea not to enforce some kind of accepted connections limit. However, I'm pessimistic about the possibility of executing arbitrary code - even if you succeed to overwrite the return address, you must think of some other way to place "evil code". Of course, nothing is impossible :)

BTW, my PoC code has some pretty dumb bug, char hostname[12] should be char hostname[15]...stupid me, I forgot about the dots in the ip address :)