From: Arjan van de Ven <arjanv@redhat.com>
To: Robinson Maureira Castillo <rmaureira@alumno.inacap.cl>
Cc: Andrus <andrus@members.ee>, linux-kernel@vger.kernel.org
Subject: Re: Kernels 2.2 and 2.4 exploit (ALL VERSION WHAT I HAVE TESTED UNTILL NOW!)
Date: 19 Mar 2003 15:28:00 +0100 [thread overview]
Message-ID: <1048084079.1493.6.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303191012320.3319-100000@alumno.inacap.cl>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Wed, 2003-03-19 at 15:13, Robinson Maureira Castillo wrote:
> On Wed, 19 Mar 2003, Andrus wrote:
> > You can download working exploit on
> > http://www.members.ee/ptrace-exploit.c
> >
> > Its hell long exploit as I know, and still not patched!
> >
>
> I have it, it's no longer on that URL, but I test it against the last
> errata kernel from RedHat and it's not vulnerable.
>
> [rmaureira@linux rmaureira]$ ./ptrace-xploit
> [-] Unable to attach: Operation not permitted
> Killed
there is some misunderstanding about at least one of the exploits out
there; one of them will, when successful, make itself setuid-root....
result:
admin tries exploit, succeeds
admin updates kernel to fixed one
admin tries exploit, gets root again due to setuid-root and thinks the
kernel is not fixed
admin yells at $vendor for providing a broken fix
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-19 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 13:54 Andrus
2003-03-19 14:13 ` Robinson Maureira Castillo
2003-03-19 14:28 ` Arjan van de Ven [this message]
2003-03-19 15:27 ` Alan Cox
2003-03-19 14:44 ` BODA Karoly jr.
2003-03-19 16:00 ` BODA Karoly jr.
2003-03-19 14:55 ` Anders Gustafsson
2003-03-19 16:13 ` Alan Cox
2003-03-19 15:28 ` Anders Gustafsson
2003-03-20 3:18 ` Rick Warner
2003-03-20 17:15 ` mix
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=1048084079.1493.6.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=andrus@members.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=rmaureira@alumno.inacap.cl \
/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®