From: Luca Venturini <luca@yepa.com>
To: linux-kernel@vger.kernel.org
Cc: "mazzaro@inwind.it" <mazzaro@inwind.it>, alan.cox@linux.org
Subject: Re: URGENT: Bug in ptrace()
Date: Tue, 24 Jul 2001 21:15:37 +0200 [thread overview]
Message-ID: <3B5DC959.7C3CCB8F@yepa.com> (raw)
In-Reply-To: <GGZG1N$IUdIOnzYcrd2i0brgDIkl7XCtbAQK_Zw0pdyqLQY9plM@inwind.it>
Hi all,
I patched it for kernel 2.2.12 and 2.2.19:
just replace
if ((!child->dumpable ||
(current->uid != child->euid) ||
(current->uid != child->suid) ||
(current->uid != child->uid) ||
(current->gid != child->egid) ||
(current->gid != child->sgid) ||
with
if ((!child->dumpable ||
(child->suid == 0) ||
(current->uid != child->euid) ||
(current->uid != child->suid) ||
(current->uid != child->uid) ||
(current->gid != child->egid) ||
(current->gid != child->sgid) ||
in /usr/src/linux/arch/i386/kernel/ptrace.c
This way nobody can "ATTACH" with ptrace a setuited task.
I do not know if this can be useful. Maybe the gurus in
the list can say something about it.
Is it even useful for new kernels?
Thanks.
Luca Venturini
Yepa S.r.l.
"mazzaro@inwind.it" wrote:
>
> Hi all,
>
> The exploit found on http://www.securiteam.com/exploits/5NP061P4AW.html
>
> Still works on the latest 2.2 that's to say (I Think), 2.2.19
>
> How can it be?
>
> There are still a lot of machines on the net which use that ker.
>
> Thank you for your attenction...
>
> P.S.
> The exploit works even on the latest kernel (of the 2.2 series, off course), found on
> ftp://updates.redhat.com/6.2/en/
>
> P.P.S.
> I'm trying to follow the ML, but the traffic is too high for me...:-(
> So, if you can... could you answer to my address?
>
> Thank you,
>
> Silvio Mazzaro
prev parent reply other threads:[~2001-07-24 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 14:53 URGENT: Bug in ptrace() mazzaro
2001-07-24 19:15 ` Luca Venturini [this message]
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=3B5DC959.7C3CCB8F@yepa.com \
--to=luca@yepa.com \
--cc=alan.cox@linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazzaro@inwind.it \
/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