Can access to /proc/$PID/exe be relaxed?
Hi!
Unless I am mistaken a process currently needs CAP_SYS_PTRACE to read /proc/$PID/exe for abritrary processes. Does that make sense? Could that be relaxed? Is there any reason to limit access to that link at all? To me the data from /proc/$PID/cmdline seems to be far more worthy to be protected than /proc/$PID/exe, or am I missing something?
Tbh, looking at the code I don't really get where CAP_SYS_PTRACE seems to be required, but experimenting from userspace this seems to be the case.
Lennart
Signature · 3 lines
Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
Quoted 4 lines · Lennart Poettering
Hi!
Unless I am mistaken a process currently needs
CAP_SYS_PTRACEto read/proc/$PID/exefor abritrary processes.
You mean "readlink'?
Quoted 8 lines
Does that make sense? Could
that be relaxed? Is there any reason to limit access to that link at all? To me the data from/proc/$PID/cmdlineseems to be far more worthy to be protected than/proc/$PID/exe, or am I missing something?Tbh, looking at the code I don't really get where
CAP_SYS_PTRACEseems to be required, but experimenting from userspace this seems to be the case.
Another annoying thing is that sometimes processes cannot open their own /proc/self/fd/N. Example:
# setuidgid 200:200 cat /proc/self/fd/0 cat: /proc/self/fd/0: Permission denied
In real life this happened when I wanted to redirect apache's log to stderr. The config directive only allowed redirecting to a file, so I specified /proc/self/fd/2. It does not work if apache drops root after startup.
--
vda
Quoted 8 lines · Denys Vlasenko
Quoted 4 lines · Lennart Poettering
Hi!
Unless I am mistaken a process currently needs
CAP_SYS_PTRACEto read/proc/$PID/exefor abritrary processes.You mean "readlink'?
Yes.
Lennart
Signature · 3 lines
Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4