From: Torsten Duwe <duwe@caldera.de>
To: Chris Evans <chris@scary.beasts.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modprobe local root exploit
Date: Mon, 13 Nov 2000 19:11:51 +0100 (CET) [thread overview]
Message-ID: <14864.12007.216381.254700@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0011131655430.22139-100000@ferret.lmh.ox.ac.uk>
In-Reply-To: <14864.6812.849398.988598@ns.caldera.de> <Pine.LNX.4.21.0011131655430.22139-100000@ferret.lmh.ox.ac.uk>
>>>>> "Chris" == Chris Evans <chris@scary.beasts.org> writes:
Chris> What's wrong with isalnum() ?
Hm, must admit that I wasn't 100% sure if that's in the kernel lib or an evil
gcc expands it inline to some static array lookup. Now I see that it's
already in the kernel. Do some of you also sometimes wonder why the kernel is
so big ;-) ?
OK, so let's go for the isalnum() version, and don't forget to
#include <linux/ctype.h>
above...
Torsten
For those who joined the program late here's the complete patch:
--- linux/kernel/kmod.c.orig Tue Sep 26 01:18:55 2000
+++ linux/kernel/kmod.c Mon Nov 13 19:09:11 2000
@@ -18,6 +18,7 @@
#include <linux/config.h>
#include <linux/sched.h>
#include <linux/unistd.h>
+#include <linux/ctype.h>
#include <linux/smp_lock.h>
#include <asm/uaccess.h>
@@ -168,6 +169,19 @@
static atomic_t kmod_concurrent = ATOMIC_INIT(0);
#define MAX_KMOD_CONCURRENT 50 /* Completely arbitrary value - KAO */
static int kmod_loop_msg;
+ const char * p;
+
+ /* For security reasons ensure the requested name consists
+ * only of allowed characters. Especially whitespace and
+ * shell metacharacters might confuse modprobe.
+ */
+ for (p = module_name; *p; p++)
+ {
+ if (isalnum(*p) || *p == '_' || *p == '-')
+ continue;
+
+ return -EINVAL;
+ }
/* Don't allow request_module() before the root fs is mounted! */
if ( ! current->fs->root ) {
-
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-13 18:12 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 [this message]
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
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=14864.12007.216381.254700@ns.caldera.de \
--to=duwe@caldera.de \
--cc=Torsten.Duwe@caldera.de \
--cc=chris@scary.beasts.org \
--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