lkml.org 
[lkml]   [2011]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 2/2] fs, proc: Introduce the /proc/<pid>/map_files/ directory v12
> No, I mean something else.  Assume you have a task, which does the
> steps:
>
> 1) opens some sensitive file as root. This file is e.g. 0700.
>
> 2) mmaps the file via opened fd, either RO or RW.
>
> 3) closes fd.
>
> 4) drops root.
>
> Now it has a mapping of a privileged file, but cannot get fd of it
> anyhow. With map_files/ he may open his own /proc/$$/map_files/, pass
> ptrace() check, and get fd of the privileged file. He cannot explicitly
> open it as it is 0700, but he may open it via map_files/ and get RO/RW
> fd.
>

What is the problem here - the fact that we have some file considered to
be private be open-able by somebody else, or the fact that we can truncate
the file being mapped?

If the fist issue stands, then it also stands for /proc/pid/fd and thus we
don't introduce the new problem.

If the second, then it's not a problem as mm can handle this already.

Thanks,
Pavel


\
 
 \ /
  Last update: 2011-09-14 18:19    [W:0.135 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site