Skip to content

Commit

Permalink
fcaps: clear the same personality flags as suid when fcaps are used
Browse files Browse the repository at this point in the history
If a process increases permissions using fcaps all of the dangerous
personality flags which are cleared for suid apps should also be cleared.
Thus programs given priviledge with fcaps will continue to have address space
randomization enabled even if the parent tried to disable it to make it
easier to attack.

Signed-off-by: Eric Paris <eparis@redhat.com>
Reviewed-by: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>
  • Loading branch information
eparis authored and James Morris committed Apr 18, 2012
1 parent 09c79b6 commit d52fc5d
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions security/commoncap.c
Original file line number Diff line number Diff line change
Expand Up @@ -505,6 +505,11 @@ int cap_bprm_set_creds(struct linux_binprm *bprm)
}
skip:

/* if we have fs caps, clear dangerous personality flags */
if (!cap_issubset(new->cap_permitted, old->cap_permitted))
bprm->per_clear |= PER_CLEAR_ON_SETID;


/* Don't let someone trace a set[ug]id/setpcap binary with the revised
* credentials unless they have the appropriate permit
*/
Expand Down

0 comments on commit d52fc5d

Please sign in to comment.