Re: [Full-disclosure] SSH brute force blocking tool
- From: gabriel rosenkoetter <gr@xxxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 16:34:06 -0500
On Mon, Nov 27, 2006 at 09:29:33PM +0000, Tavis Ormandy wrote:
Gabriel, I was referring to this line:
awk '!/#/ && /\./ && !a[$0]++
{print "iptables -A INPUT -s "$1" -i eth0 -d '$ifaddr' -p TCP --dport 22
-j REJECT"}' /etc/hosts.deny |\
awk '/iptables/ && !/#/ && !/-s -i/'|sh
(note the |sh), $1 can be controlled by specially crafted attempted
logins.
Aha.
Yep, sure can!
I couldn't find where the malicious input was actually executed, but
I didn't spend long looking.
I take back my take back.
--
gabriel rosenkoetter
gr@xxxxxxxxxxxx
Attachment:
pgpgky43zvaa9.pgp
Description: PGP signature
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
- Follow-Ups:
- Re: [Full-disclosure] SSH brute force blocking tool
- From: Michael Holstein
- Re: [Full-disclosure] SSH brute force blocking tool
- References:
- Re: [Full-disclosure] SSH brute force blocking tool
- From: Tavis Ormandy
- Re: [Full-disclosure] SSH brute force blocking tool
- From: J. Oquendo
- Re: [Full-disclosure] SSH brute force blocking tool
- From: Tavis Ormandy
- Re: [Full-disclosure] SSH brute force blocking tool
- From: J. Oquendo
- [Full-disclosure] SSH brute force blocking tool
- From: J. Oquendo
- Re: [Full-disclosure] SSH brute force blocking tool
- From: gabriel rosenkoetter
- Re: [Full-disclosure] SSH brute force blocking tool
- From: gabriel rosenkoetter
- Re: [Full-disclosure] SSH brute force blocking tool
- From: Tavis Ormandy
- Re: [Full-disclosure] SSH brute force blocking tool
- Prev by Date: Re: [Full-disclosure] SSH brute force blocking tool
- Next by Date: Re: [Full-disclosure] SSH brute force blocking tool
- Previous by thread: Re: [Full-disclosure] SSH brute force blocking tool
- Next by thread: Re: [Full-disclosure] SSH brute force blocking tool
- Index(es):