BugTraq
Apache hacks (./atac, d0s.txt) Apr 29 2005 07:03PM
Andrew Y Ng (ayn AndrewNg com) (10 replies)
Re: Apache hacks (./atac, d0s.txt) May 01 2005 03:11AM
a.list.address (at) gmail (dot) com [email concealed] (a list address gmail com) (1 replies)
Re: Apache hacks (./atac, d0s.txt) May 02 2005 09:35PM
Nick Bright (nick-tech terraworld net)
Re: Apache hacks (./atac, d0s.txt) Apr 30 2005 07:46AM
Chris Umphress (umphress gmail com)
Re: Apache hacks (./atac, d0s.txt) Apr 30 2005 07:17AM
Sagiko (sagiko gmail com)
Re: Apache hacks (./atac, d0s.txt) Apr 30 2005 04:48AM
Daniel Cid (danielcid yahoo com br)
Re: Apache hacks (./atac, d0s.txt) Apr 30 2005 01:55AM
Luiz Henrique (luizhwk inf ufsc br)
Re: Apache hacks (./atac, d0s.txt) Apr 29 2005 11:33PM
Skip Carter (skip taygeta com)
Re: Apache hacks (./atac, d0s.txt) Apr 29 2005 11:21PM
Robert Zilbauer (zilbauer slappy org)
Re: Apache hacks (./atac, d0s.txt) Apr 29 2005 09:49PM
Jay D. Dyson (jdyson treachery net)
Re: Apache hacks (./atac, d0s.txt) Apr 29 2005 09:45PM
KF (lists) (kf_lists digitalmunition com)
Re: Apache hacks (./atac, d0s.txt) Apr 29 2005 09:36PM
Steve Kemp (steve steve org uk)
On Fri, Apr 29, 2005 at 02:03:58PM -0500, Andrew Y Ng wrote:

> My server has been seeing some usual activities today, I don't have much time
> to get down to the bottom of things, but after I investigated briefly I have
> decided to disable PERL executable permission for www-data (Apache process's
> user), also locked /var/tmp so www-data cannot write to it.

Use chrot to protect your server slightly more against problems
with any buggy scripts.

This is almost certainly the result of an insecue PHP, Perl, or
other CGI script - rather than an Apache hack.

If you examine your webservers logs you might see where the
attack happened, perhaps you'll have entries invoking the
'wget' command to download the script you found from a remote
server - that's often a common attack.

If you're interested in protecting your server against input
designed to attack insecure applications you might wish to
investigate 'mod_security'.

mod-security homepage:
http://www.modsecurity.org/

mod-security under Debian example:
http://www.debian-administration.org/?article=65

> Looks like it ignores all the `kill` signals, not sure how I can actually
> kill it...

As root.

> here's d0s.txt:

Connects to an irc server, forking to make its name less obvious
on the process list.

Steve
--
# Debian System Administration
www.debian-administration.org/

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus