lkml.org 
[lkml]   [2000]   [Nov]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Modprobe local root exploit
From
Date
Keith Owens <kaos@ocs.com.au> writes:

> All these patches against request_module are attacking the problem at
> the wrong point.

Agreed.

> The kernel can request any module name it likes, using any string it
> likes, as long as the kernel generates the name. The real problem
> is when the kernel blindly accepts some user input and passes it
> straight to modprobe, then the kernel is acting like a setuid
> wrapper for a program that was never designed to run setuid.

I don't think it's a good idea to distribute such stuff over the whole
kernel. Better control it at a single place, either when passing the
parameter down to modprobe, or in modprobe itself. Everything else is
too error-prone.

--
Florian Weimer Florian.Weimer@RUS.Uni-Stuttgart.DE
University of Stuttgart http://cert.uni-stuttgart.de/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:45    [W:0.081 / U:2.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site