Skip to main content

apache 2.2 - Block traffic behind AWS ELB

My web servers are behind ELB, I want to block traffic
from some specific user agent which is a DDOS attack. Apache always see ip address of
ELB as an end user so I tried below
attempts:




  1. Blocking IP
    address at ELB level is not possible because it has limit of 20 IP addresses and IP
    addresses change at every attack.

  2. Block access
    using rewrite condition, this works but if lot of hits come then server load goes beyond
    100 and all apache threads become busy in serving tons of 403 so site appears down for
    legitimate
    requests.




    RewriteCond
    %{HTTP_USER_AGENT} ^SomeThing

    RewriteRule ^(.*)$ -
    [F]

  3. Block
    with mod_sec does same thing of serving 403 which create same effect as #2
    above.


  4. Block packets with iptables
    string module: Block packets which have specific user agent. In this scenario iptables
    sends DROP/ REJECT to attacker, apache doesn't get signal that the connections is now
    dead and waits for a timeout which cause all apache threads in use for timeout, so this
    method is not useful
    here.



    iptables -I INPUT -i eth0 -p
    tcp --dport 80 -m string --algo bm --string 'user-agent: SomeThing' -j
    REJECT




Can
I use iptables such way that it will get IP address from first packet which has
user-agent: SomeThing and block all the next packets which has
X-Forwarded-For: someIP for 4-5 hours. I don't want to keep the
IP address blocking always as these IP Addresses can be assigned to some legitimate
users and that will be blocked.



Or is there any
other better way to handle this attack ?

Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able