From: Keith Owens <kaos@ocs.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modprobe local root exploit
Date: Thu, 16 Nov 2000 17:14:54 +1100 [thread overview]
Message-ID: <10170.974355294@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "15 Nov 2000 22:04:47 -0800." <8uvtdv$c3q$1@cesium.transmeta.com>
On 15 Nov 2000 22:04:47 -0800,
"H. Peter Anvin" <hpa@zytor.com> wrote:
>No, it's correct, actually, but probably not what you want. It will
>include all letters [A-Za-z], but if a module named "ärlig"...
Trying to sanitise the module name in request_module is the wrong fix
anyway, the kernel can ask for any module name it likes. What it must
not do is treat user supplied input _unchanged_ as a module name.
modutils 2.3.20 (just released) fixes all the known local root
exploits, without kernel changes. However 2.3.20 does nothing about
this problem: "ping6 -I module_name" which lets any user load any
module. That problem exists because the kernel passes user supplied
data unchanged to request_module. The only fix is to add a prefix to
user supplied input (say 'user-interface-') before passing the text to
request_module. This has to be fixed in the higher layers of the
kernel, it cannot be fixed in request_module or modprobe.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-16 6:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 14:37 Modprobe local root exploit Gregory Maxwell
2000-11-13 16:26 ` Torsten Duwe
2000-11-13 16:44 ` Francis Galiegue
2000-11-13 16:45 ` Torsten Duwe
2000-11-13 16:56 ` Chris Evans
2000-11-13 17:21 ` Jan Dvorak
2000-11-13 18:11 ` Torsten Duwe
2000-11-14 5:02 ` Peter Samuelson
2000-11-14 5:50 ` Keith Owens
2000-11-14 9:19 ` Florian Weimer
2000-11-14 10:42 ` Malcolm Beattie
2000-11-14 10:54 ` Jakub Jelinek
2000-11-14 11:58 ` Chris Evans
2000-11-14 10:58 ` Keith Owens
2000-11-14 12:28 ` Nick Holloway
2000-11-14 14:01 ` David Woodhouse
2000-11-14 1:35 ` Horst von Brand
2000-11-13 19:46 ` Peter Samuelson
2000-11-14 11:29 ` Daniel Phillips
2000-11-14 14:23 ` Daniel Phillips
2000-11-14 16:25 ` David Relson
2000-11-15 4:09 ` Horst von Brand
2000-11-16 5:22 ` Alan Cox
2000-11-16 6:04 ` H. Peter Anvin
2000-11-16 6:14 ` Keith Owens [this message]
2000-11-16 6:16 ` H. Peter Anvin
2000-11-16 14:12 ` Torsten Duwe
2000-11-16 15:07 ` 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=10170.974355294@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=hpa@zytor.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