From: Frank van Maarseveen <frankvm@xs4all.nl>
To: Keith Whyte <keith@media-solutions.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 fork & defunct child => system is hacked
Date: Tue, 18 Nov 2003 11:39:07 +0100 [thread overview]
Message-ID: <20031118103907.GA23644@iapetus.localdomain> (raw)
In-Reply-To: <3FB96718.20103@media-solutions.ie>
On Mon, Nov 17, 2003 at 06:26:00PM -0600, Keith Whyte wrote:
>
> { strace listing deleted, see
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106905386725308&w=2 }
First of all, /bin/true doing a fork() basically means you've
been hacked: there should not be any such code in there. The
open("/proc/17904///////////exe" is anouther piece of clear evidence
that your system has been hacked.
Why the additional slashes?
I suspect a library/or LD_PRELOAD hack which simply encodes the getpid()
return value in decimal notation and stores it right into a static
buffer containing
"/proc//////////////////exe"
because it can't use sprintf at that point for some reason (maybe
just because it is a library/LD_PRELOAD hack).
--
Frank
next prev parent reply other threads:[~2003-11-18 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 7:18 2.4.18 fork & defunct child Keith Whyte
[not found] ` <3FB8E40F.EF61CA7@gmx.de>
2003-11-18 0:26 ` Keith Whyte
2003-11-18 1:00 ` Maciej Zenczykowski
2003-11-18 10:39 ` Frank van Maarseveen [this message]
2003-11-19 19:45 ` 2.4.18 fork & defunct child => system is hacked Keith Whyte
2003-11-20 2:42 ` solution: 2.4.18 fork & defunct child Keith Whyte
[not found] ` <20031117184732.GA531@louise.pinerecords.com>
2003-11-18 0:41 ` Keith Whyte
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=20031118103907.GA23644@iapetus.localdomain \
--to=frankvm@xs4all.nl \
--cc=keith@media-solutions.ie \
--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®