From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: TRG vger.timpanogas.org hacked
Date: Mon, 4 Jun 2001 18:36:42 -0700 [thread overview]
Message-ID: <20010604183642.A855@vger.timpanogas.org> (raw)
Our master server (vger.timpanogas.org) running 2.2.19 was hacked and
completely obliterated by someone using a Novell Proxy Cache via a kernel
level exploit in [sys_wait+4]. They somehow created a segmentation fault
down inside the kernel, then gained access to the /lib directory and
relinked the libraries to a set of bogus libs, which gave them
access to the server. Only public code and email is processed on
this server.
For those interested in reviewing this attack, I have the entire previous
hard disk available and can mount it under the public ftp area if anyone
is curious as to how these folks did this. They exploited BIND 8.2.3
to get in and logs indicated that someone was using a "back door" in
Novell's NetWare proxy caches to perform the attack (since several
different servers were used as "blinds" to get in).
We are unable to determine just how they got in exactly, but they
kept trying and created an oops in the affected code which allowed
the attack to proceed.
Jeff
next reply other threads:[~2001-06-05 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 1:36 Jeff V. Merkey [this message]
2001-06-05 7:05 ` TRG vger.timpanogas.org hacked Alan Cox
2001-06-05 10:14 ` Daniel Roesen
2001-06-05 14:10 ` Michael H. Warfield
2001-06-05 18:30 ` Jeff V. Merkey
2001-06-05 18:42 ` Michael H. Warfield
2001-06-05 13:07 ` Henning P. Schmiedehausen
2001-06-05 13:41 ` Daniel Roesen
-- strict thread matches above, loose matches on Subject: below --
2001-06-05 10:33 Randal, Phil
2001-06-05 11:07 ` Matti Aarnio
2001-06-05 17:19 ` Brian Wellington
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=20010604183642.A855@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.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