From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Rootkit queston
Date: Mon, 1 Dec 2003 17:19:30 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0312011649060.4785@chaos> (raw)
In-Reply-To: <1070313094.11356.6.camel@midux>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 2152 bytes --]
On Mon, 1 Dec 2003, Markus [ISO-8859-1] Hästbacka wrote:
> Hello all!
>
> I've been wondering about what is a rootkit and how it works?
It's some crap thrown together for the express purpose of
running a command-shell with root privileges on a system
being attacked. The binary load is usually fed in using
some kind of exploit such as overwriting a buffer in some
privileged program.
You fix that problem by upgrading any program found to
be susceptible to attack. If you have an old system, you
might wish to upgrade:
inetd
sendmail
ftpd
tftpd
/usr/sbin/in.*
dump
... and any other program that runs suid.
In particular, do not run inetd. Run xinetd instead.
You can check for a common 'root attack', if you have inetd,
by looking at the last few lines in /etc/inetd.conf.
It may have some access port added that allows anybody
who knows about it to log in as root from the network.
It will look something like this:
# End of inetd.conf.
4002 stream tcp nowait root /bin/bash --
In this case, port 4002 will allow access to a root shell
that has no terminal processing, but an attacker can use this
to get complete control of your system. FYI, this is a 5-year-old
attack, long obsolete if you have a "store-bought" distribution
more recent.
> I've been paranoid after I heard that the debian project got
> "rootkitted", I ran chkrootkit, and it said that it's possible that I
> have a LKM rootkit installed, but the website told me that it's possible
> that the LKM test gives wrong information with recent kernels (Running
> 2.4.22 now).
>
> These processes "were hidden from ps command":
> root 0 0.0 0.0 0 0 ? SWN Oct28 0:01
> [ksoftirqd_CPU0]
> root 0 0.0 0.0 0 0 ? SW Oct28 4:27 [kswapd]
> root 0 0.0 0.0 0 0 ? SW Oct28 0:00 [bdflush]
> root 0 0.0 0.0 0 0 ? SW Oct28 0:01
> [kupdated]
>
> They seem to have PID 0, is this normal?
Yes. These are kernel threads.
[SNIPPED...]
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-12-01 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 21:11 Markus Hästbacka
2003-12-01 22:19 ` Richard B. Johnson [this message]
2003-12-01 23:36 ` Måns Rullgård
2003-12-01 23:47 ` Mike Fedyk
2003-12-01 22:48 ` Bernd Eckenfels
2003-12-05 17:29 ` dean gaudet
2003-12-02 21:24 Albert Cahalan
2003-12-06 13:45 Samium Gromoff
2003-12-06 15:01 ` Måns Rullgård
2003-12-06 15:10 ` Doug McNaught
2003-12-06 15:07 ` Christian
2003-12-08 13:49 ` Richard B. Johnson
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=Pine.LNX.4.53.0312011649060.4785@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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
all inboxes | Powered by JetHome®