Bug#764449: core.5: please mention security implications of /proc/sys/kernel/core_pattern

2017-09-29 Thread Michael Kerrisk (man-pages)
After, looking at this for quite a while, I am not convinced there's an issue here. %e is returned as just the basename of the executable path, and %t and %E seem even less problematic. If you think there's an issue, it would be good to show a worked example of how an "innocent" core_pattern pipe

Bug#764449: core.5: please mention security implications of /proc/sys/kernel/core_pattern

2014-10-08 Thread Enrico Zini
Package: manpages Version: 3.71-1 Severity: normal Hello, man 5 core gingerly mentions piping core dumps to a program and using % specifiers as arguments. It does not, however, mention their escaping, or lack thereof. I am not terribly bothered by scenarios like this here:

Bug#764449: core.5: please mention security implications of /proc/sys/kernel/core_pattern

2014-10-08 Thread Enrico Zini
On Wed, Oct 08, 2014 at 10:02:52AM +0200, Enrico Zini wrote: %e, %E and %h look harmful to me in that way, with a risk of opening user-exploitable vulnerabilities: It's also worth mentioning that most of that information can be found anyway, and in a safer way, via /proc/%p/, but that