All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: linux-security-module@vger.kernel.org, linux-audit@redhat.com
Cc: Richard Guy Briggs <rgb@redhat.com>,
	Andy Lutomirski <luto@kernel.org>,
	"Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
	Kees Cook <keescook@chromium.org>,
	James Morris <james.l.morris@oracle.com>,
	Eric Paris <eparis@redhat.com>, Paul Moore <pmoore@redhat.com>,
	Steve Grubb <sgrubb@redhat.com>
Subject: [PATCH] capabilities: do not audit log BPRM_FCAPS on set*id
Date: Thu,  2 Mar 2017 20:10:29 -0500	[thread overview]
Message-ID: <515427654218b7ce22441f635115e93cf74d6302.1488491988.git.rgb@redhat.com> (raw)

The audit subsystem is adding a BPRM_FCAPS record when auditing setuid
application execution (SYSCALL execve). This is not expected as it was
supposed to be limited to when the file system actually had capabilities
in an extended attribute.  It lists all capabilities making the event
really ugly to parse what is happening.  The PATH record correctly
records the setuid bit and owner.  Suppress the BPRM_FCAPS record on
set*id.

See: https://github.com/linux-audit/audit-kernel/issues/16

Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
---
 security/commoncap.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/security/commoncap.c b/security/commoncap.c
index 14540bd..8f6bedf 100644
--- a/security/commoncap.c
+++ b/security/commoncap.c
@@ -594,16 +594,17 @@ skip:
 	/*
 	 * Audit candidate if current->cap_effective is set
 	 *
-	 * We do not bother to audit if 3 things are true:
+	 * We do not bother to audit if 4 things are true:
 	 *   1) cap_effective has all caps
 	 *   2) we are root
 	 *   3) root is supposed to have all caps (SECURE_NOROOT)
+	 *   4) we are running a set*id binary
 	 * Since this is just a normal root execing a process.
 	 *
 	 * Number 1 above might fail if you don't have a full bset, but I think
 	 * that is interesting information to audit.
 	 */
-	if (!cap_issubset(new->cap_effective, new->cap_ambient)) {
+	if (!is_setid && !cap_issubset(new->cap_effective, new->cap_ambient)) {
 		if (!cap_issubset(CAP_FULL_SET, new->cap_effective) ||
 		    !uid_eq(new->euid, root_uid) || !uid_eq(new->uid, root_uid) ||
 		    issecure(SECURE_NOROOT)) {
-- 
1.7.1

             reply	other threads:[~2017-03-03  2:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  1:10 Richard Guy Briggs [this message]
2017-03-03  2:07 ` [PATCH] capabilities: do not audit log BPRM_FCAPS on set*id Serge E. Hallyn
2017-03-03  2:50   ` Richard Guy Briggs
2017-03-07 17:22     ` Richard Guy Briggs
2017-03-07 18:10       ` Serge E. Hallyn
2017-03-07 21:10         ` Richard Guy Briggs
2017-03-07 21:25           ` Serge E. Hallyn
2017-03-09 14:34           ` Steve Grubb
2017-03-09 14:34             ` Steve Grubb
2017-03-29 10:29             ` Richard Guy Briggs
2017-03-29 10:29               ` Richard Guy Briggs
2017-04-11 19:36               ` Paul Moore
2017-04-11 19:36                 ` Paul Moore
2017-04-12  6:43                 ` Richard Guy Briggs
2017-04-12  6:43                   ` Richard Guy Briggs
2017-04-12 14:51                   ` Serge E. Hallyn
2017-04-12 14:51                     ` Serge E. Hallyn
2017-04-12 18:49                   ` Steve Grubb
2017-04-12 18:49                     ` Steve Grubb
2017-04-13  8:50                     ` Richard Guy Briggs
2017-04-13  8:50                       ` Richard Guy Briggs
2017-04-13 19:36                       ` Steve Grubb
2017-04-13 19:36                         ` Steve Grubb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515427654218b7ce22441f635115e93cf74d6302.1488491988.git.rgb@redhat.com \
    --to=rgb@redhat.com \
    --cc=eparis@redhat.com \
    --cc=james.l.morris@oracle.com \
    --cc=keescook@chromium.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=pmoore@redhat.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=sgrubb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.