From: linux-kernel-owner@vger.kernel.org
To: <linux-kernel@vger.kernel.org>
Subject: PROBLEM: Intruders kidnapping PIDs of server processes
Date: Mon, 10 Mar 2003 12:17:44 +0100 [thread overview]
Message-ID: <004b01c2e6f6$ace35c80$827ba8c0@mttw.net> (raw)
Intruders kidnapping PIDs of server processes
Problem/Background:
Recently our system was under attack by intruders using trojan code to
gain access to our system. Apparently they where trying to get one of
our servers to route IRC-traffic using psyBNC.
It seems like the intruders, probably using reppid to take over processes,
could hide their own processes in existing ones. Doing something like
ps -gaux won't show anything strange at all!
This makes it impossible to find and shut off unwanted processes.
Using netstat I could clearly see that "something" was listening on
ports that I didn't recognize. Doing netstat -ap only showed a dash '-'
instead of any process owning the socket.
Software:
The server was running Linux Redhat 7.2 (Kernel 2.4.7-10). Unfortunately
I cannot get anymore specific because the intruders seems to have rendered
the system unbootable before I had any chance of gathering info for
this report. But this bug (or feature) seems to affect all kernels,
regardless
of version.
Solution?
Is there anyway to fix this "bug" or is it a built-in feature. So that
software
like reppid simply can't take over an existing PID.
Sources:
Probably the intruders have been using something similar to the program
Reppid found at http://www.psychoid.lam3rz.de/reppid.c.
I would be grateful for an answer, even a simple "No,
it's not a bug, it's a feature" would help.
TIA
Carl Oeberg, (webmaster@gitte.nu)
reply other threads:[~2003-03-10 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='004b01c2e6f6$ace35c80$827ba8c0@mttw.net' \
--to=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®