Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Joel Newkirk <netfilter@newkirk.us>
To: netfilter@lists.samba.org
Subject: Re: IPTBLE rule for Slapper" Linux Worm
Date: Fri, 20 Sep 2002 00:44:24 -0400	[thread overview]
Message-ID: <200209200044.24379.netfilter@newkirk.us> (raw)
In-Reply-To: <00cf01c26051$9a2a5c00$0200000a@ramasamy>

On Thursday 19 September 2002 10:56 pm, Sundaram wrote:
> What is the IP rule, I have set for following worm??
>
>
> Security Alert: Eradicating the "Slapper" Linux Worm
>
> http://www.extremetech.com/article2/0,3973,538734,00.asp

(rules example below)
Inbound 443 is the most useful of these, IF you can do it, since the others depend
on the machine already being infected, which you can easily and quickly determine
yourself just after you start blocking inbound port 443, the infection vector.
Just "ls -a /tmp" and make sure there's no ".bugtraq" or ".bugtraq.c" there.
If they are you're already infected.

ExtremeTech tells us:
   Delete the files if they are already present. Do "mkdir -m a= /tmp/.bugtraq" and 
   "mkdir -m a= /tmp/.bugtraq.c", then reboot if you were already infected.  
   The permissionless directories prevent an incoming infection from taking up residence. 

They fails to mention that three seconds with an editor will create a version that 
saves itself under different names, but still partakes of the same DDoS network.

(Symantec tells us: * Run LiveUpdate, which is the easiest way to obtain virus definitions :^)

If we want to be helpful, we can log any attempt to connect to us on UDP 2002,
meaning the source is infected and thinks we are/were, and notify those servers
that they appear to be infected.


# Block "Linux.Slapper.Worm" or "apache/mod_ssl worm"
#
# log & drop any inbound packets for UDP port 2002, 
# prevents already infected system receiving instructions.
# this should only happen if we are/were infected.
# If we're feeling charitable, let the source of any 2002
# packets know that they are probably infected as well.  :^)
/sbin/iptables -A INPUT -p UDP --dport 2002 -j LOG
/sbin/iptables -A INPUT -p UDP --dport 2002 -j DROP
#
# Block inbound port 443 (Infection point) ONLY if you don't
# need to serve HTTPS from machine.
/sbin/iptables -A INPUT -p TCP --dport 443 REJECT
#
# Block outbound port 443 ONLY if you don't need to browse 
# to HTTPS from this machine.
# This blocks an already infected system from propogating.
/sbin/iptables -A OUTPUT -p TCP --dport 443 -j REJECT
#

# j


      reply	other threads:[~2002-09-20  4:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20  2:56 IPTBLE rule for Slapper" Linux Worm Sundaram
2002-09-20  4:44 ` Joel Newkirk [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=200209200044.24379.netfilter@newkirk.us \
    --to=netfilter@newkirk.us \
    --cc=netfilter@lists.samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox