How useful is mounting /tmp noexec?

Posted by Novelocrat on Server Fault See other posts from Server Fault or by Novelocrat
Published on 2009-10-07T23:43:37Z Indexed on 2011/01/10 19:55 UTC
Read the original article Hit count: 234

Filed under:
|
|
|
|

Many people (including the Securing Debian Manual) recommend mounting /tmp with the noexec,nodev,nosuid set of options. This is generally presented as one element of a 'defense-in-depth' strategy, by preventing the escalation of an attack that lets someone write a file, or an attack by a user with a legitimate account but no other writable space.

Over time, however, I've encountered arguments (most prominently by Debian/Ubuntu Developer Colin Watson) that noexec is a useless measure, for a couple potential reasons:

  1. The user can run /lib/ld-linux.so <binary> in an attempt to get the same effect.
  2. The user can still run system-provided interpreters on scripts that can't be run directly

Given these arguments, the potential need for more configuration (e.g. debconf likes an executable temporary directory), and the potential loss of convenience, is this a worthwhile security measure? What other holes do you know of that enable circumvention?

© Server Fault or respective owner

Related posts about linux

Related posts about security