From: Rudi Starcevic <tech@wildcash.com>
To: ebaar@purdue.edu
Cc: netfilter@lists.netfilter.org
Subject: Re: Virus Attack & String Matching
Date: Fri, 06 Aug 2004 16:21:56 +1000 [thread overview]
Message-ID: <41132384.9000601@wildcash.com> (raw)
In-Reply-To: <54a712f004080523095fc37bee@mail.gmail.com>
Hi Erik,
You can use mod_security, http://www.modsecurity.org/,
to match strings and drop packets for your Apache web server.
An option is to use Iptables for rate limiting and mod_security
for string matching and http deny.
This is my tatic, would be keen to hear of any better techniques.
HTH
Kind regards,
Rudi.
erikbaar@gmail.com wrote:
> Hello,
>
> I've recently had to setup string matching to save a sever that was
> the subject of a virus DDOS attack, two of the domains on the server
> were recieving thousands of HTTP Get requests. After setting up a
> limit rule to slow it down and patch the kernel, I setup a filter like
> this:
>
> iptables -I INPUT -p tcp -d DEST_IP --dport -m string --string "GET
> /1.jpg" -j DROP
> iptables -I INPUT -p tcp -d DEST_IP --dport -m string --string "GET
> /get.php" -j DROP
>
> Which dropped the traffic but caused Apache to generate 408 errors for
> every connection that was made. First question, is there a better or
> alternate way to do this? I've read people have recommended against
> string matching before but never found a good alternative. Second, is
> there a way I can have IP tables on a match insert a DROP rule for the
> source IP address? I wrote a script which did this based out of -j
> LOG output but would rather have it run everything automagically.
>
> Regards,
>
> Erik
>
>
>
--
Regards,
Rudi.
Internet Media Productions
prev parent reply other threads:[~2004-08-06 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 6:09 Virus Attack & String Matching erikbaar
2004-08-06 6:21 ` Rudi Starcevic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41132384.9000601@wildcash.com \
--to=tech@wildcash.com \
--cc=ebaar@purdue.edu \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.