From: Andres Salomon <dilinger@mp3revolution.net>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Flaws in recent Linux kernels
Date: Thu, 18 Oct 2001 16:25:40 -0400 [thread overview]
Message-ID: <20011018162540.B19941@mp3revolution.net> (raw)
In-Reply-To: <20011018173540.A6671@emperor.7bulls.com>
In-Reply-To: <20011018173540.A6671@emperor.7bulls.com>
When was this fixed in the 2.4 -ac series? I don't see anything in
notes.249 or notes.2410 about it.
(see http://lists.insecure.org/bugtraq/2001/Oct/0140.html for
the entire advisory)
On Thu, Oct 18, 2001 at 05:35:40PM +0000, Rafal Wojtczuk wrote:
[...]
>
> Hello,
> There are two bugs present in Linux kernels 2.2.x, x<=19 and 2.4.y,
> y<=9. The first vulnerability results in local DoS. The second one,
> involving ptrace, can be used to gain root privileges locally (in case of
> default install of most popular distributions). Linux 2.0.x is not vulnerable
> to the ptrace bug mentioned.
>
[...]
>
> III. Vendor status
> The kernel developers were notified on 18th September.
> vendor-sec at lists dot de was notified on 9th October.
>
> IV. Availability of patches.
> 2.4.12 kernel fixes both presented problems. The attached patches,
> 2.2.19-deep-symlink.patch and 2.2.19-ptrace.patch, both blessed by Linus,
> can be used to close the vulnerability in 2.2.19. The (updated)
> Openwall GNU/*/Linux kernel patches can be retrieved from
> http://www.openwall.com/linux/
> Note that the default Owl installation is not vulnerable to the ptrace bug
> described.
>
> V. The exploits
> The attached mklink.sh script creates malicious symlinks.
> ptrace-exp.c and insert_shellcode.c exploit the ptrace bug on i386
> architecture. You will probably need to adjust #define in the latter. Note
> that ptrace-exp uses LD_DEBUG variable to force a setuid program to generate
> output. This technique (stderr redirected to a pipe, LD_DEBUG set, especially
> LD_DEBUG=symbols) allows for forced suspending of a setuid binary in a
> precisely determined moments, which may be helpful to build exploits which
> rely on race-conditions. And finally, notice that under Owl LD_DEBUG is
> ignored in case of suid binaries.
>
> Save yourself,
> Nergal
> http://www.7bulls.com
>
>
--
"I think a lot of the basis of the open source movement comes from
procrastinating students..."
-- Andrew Tridgell <http://www.linux-mag.com/2001-07/tridgell_04.html>
parent reply other threads:[~2001-10-18 20:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20011018173540.A6671@emperor.7bulls.com>]
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=20011018162540.B19941@mp3revolution.net \
--to=dilinger@mp3revolution.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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®