Network Security: Detailed info on Re: [Full-disclosure] SSH brute force blocking tool

Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.

Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.

Network Security FullDisclosure

[Top] [All Lists]

Re: [Full-disclosure] SSH brute force blocking tool

from [Michael Holstein] Network Security

[Permanent Link]

Subject:	Re: [Full-disclosure] SSH brute force blocking tool
Date:	Mon, 27 Nov 2006 16:53:18 -0500

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/

[More messages with this same subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [Full-disclosure] SSH brute force blocking tool, (continued) Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, gabriel rosenkoetter Re: [Full-disclosure] SSH brute force blocking tool, Tavis Ormandy Re: [Full-disclosure] SSH brute force blocking tool, gabriel rosenkoetter Re: [Full-disclosure] SSH brute force blocking tool, Michael Holstein Re: [Full-disclosure] SSH brute force blocking tool, Joshua D. Abraham Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, gabriel rosenkoetter Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, Michael Holstein <= Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, Tonnerre Lombard Re: [Full-disclosure] SSH brute force blocking tool, Brian Eaton Re: [Full-disclosure] SSH brute force blocking tool, Thierry Zoller Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, Tavis Ormandy Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo Re: [Full-disclosure] SSH brute force blocking tool, Tavis Ormandy Re: [Full-disclosure] SSH brute force blocking tool, Thierry Zoller Re: [Full-disclosure] SSH brute force blocking tool, Tavis Ormandy

Previous by Date:	Re: [Full-disclosure] SSH brute force blocking tool, gabriel rosenkoetter
Next by Date:	Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo
Previous by Thread:	Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo
Next by Thread:	Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo
Indexes:	[Date] [Thread] [Top] [All Lists]