From: Jeremy Andrews <jeremy@kerneltrap.com>
To: linux-kernel@vger.kernel.org
Subject: DoS and Root Compromise Kernel Bug?
Date: Fri, 19 Oct 2001 14:08:53 -0400 [thread overview]
Message-ID: <20011019140853.445e5237.jeremy@kerneltrap.com> (raw)
Hello,
Yesterday Rafal Wojtczuk posted to BugTraq regarding two kernel bugs:
http://www.securityfocus.com/cgi-bin/archive.pl?id=1&mid=221337&start=2001-10-15&end=2001-10-21
I'm curious to understand more about these bugs. I.E., are they real? And,
are they fixed in 2.4.12 as claimed? How about in the -ac series?
The first kernel bug is regarding symbolic links. Rafal says it is partially
fixed in 2.4.10, and completely fixed in 2.4.12. This bug allows for a local
user to carry out a Denial of Service attack.
The second bug allows for a root compromise via ptrace. The requirements are
that /usr/bin/newgrp be suid root (as in my RedHat 7.0 server), and that newgrp
not prompt for a password when run without arguments (again, as is the case with
my RedHat 7.0 server). Rafal says the attack only appears to work on Linux.
Thanks,
-Jeremy
--
Jeremy Andrews <mailto:jeremy@kerneltrap.com>
PGP Key ID: 8F8B617A http://www.kerneltrap.com/
next reply other threads:[~2001-10-19 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 18:08 Jeremy Andrews [this message]
2001-10-21 12:42 ` Alan Cox
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=20011019140853.445e5237.jeremy@kerneltrap.com \
--to=jeremy@kerneltrap.com \
--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®