From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@osdl.org, torvalds@osdl.org
Subject: Re: [PATCH, local root on 2.4, 2.6?] compute_creds race
Date: Sat, 10 Apr 2004 12:32:04 +0200 [thread overview]
Message-ID: <87brm015uj.fsf@goat.bogus.local> (raw)
In-Reply-To: <4076F02E.1000809@myrealbox.com> (Andy Lutomirski's message of "Fri, 09 Apr 2004 11:49:18 -0700")
Andy Lutomirski <luto@myrealbox.com> writes:
> The setuid program is now running with uid=euid=500 but full permitted
> capabilities. There are two (or three) ways to effectively get local
> root now:
>
> 1. IIRC, linux 2.4 doesn't check capabilities in ptrace, so A could
> just ptrace B again.
In linux 2.4.25 there is no LSM and thus no vulnerability.
linux-2.4.25/fs/exec.c:
lock_kernel();
if (must_not_trace_exec(current)
|| atomic_read(¤t->fs->count) > 1
|| atomic_read(¤t->files->count) > 1
|| atomic_read(¤t->sig->count) > 1) {
if(!capable(CAP_SETUID)) {
bprm->e_uid = current->uid;
bprm->e_gid = current->gid;
}
if(!capable(CAP_SETPCAP)) {
new_permitted = cap_intersect(new_permitted,
current->cap_permitted);
}
}
do_unlock = 1;
Regards, Olaf.
next prev parent reply other threads:[~2004-04-10 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 18:49 [PATCH, local root on 2.4, 2.6?] compute_creds race Andy Lutomirski
2004-04-09 20:43 ` Chris Wright
2004-04-09 20:53 ` Andy Lutomirski
2004-04-10 9:16 ` Olaf Dietsche
2004-04-10 15:40 ` Andy Lutomirski
2004-04-10 18:41 ` Olaf Dietsche
2004-04-10 18:59 ` Andy Lutomirski
2004-04-10 10:32 ` Olaf Dietsche [this message]
2004-04-12 18:40 ` Chris Wright
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=87brm015uj.fsf@goat.bogus.local \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
--cc=torvalds@osdl.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