full-disclosure - Re: SSH brute force blocking tool

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <456B5E4E.6050206@csuohio.edu>
Date: Mon, 27 Nov 2006 16:53:18 -0500
From: Michael Holstein <michael.holstein@...ohio.edu>
CC: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: SSH brute force blocking tool

> That specially crafted attempt would be a HUGE raping of TCP/IP. How do 
> you supposed it would be possible for someone to insert 0wn3ed or any 
> other variable outside of an IP address?

Remember the (in)famous quote "...that vulnerability is purely 
theoretical..."?

I think the point is you don't use $language to split a bunch of fields, 
and then pipe them back through /bin/sh without making sure they're not 
malicious.

Doesn't matter that you can't think of a way to make them malicious .. 
somebody else will find one. It's safer to just assume it'll happen and 
always sanitize variables before you {do_stuff;} with them.

(my $0.02)

~Mike.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/