mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	eldad@fogrefinery.com, Jiri Kosina <jkosina@suse.cz>,
	jgunthorpe@obsidianresearch.com,
	Dan Rosenberg <dan.j.rosenberg@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	George Spelvin <linux@horizon.com>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] vsprintf: Check real user/group id for %pK
Date: Tue, 08 Oct 2013 17:49:18 -0700	[thread overview]
Message-ID: <1381279758.23937.42.camel@joe-AO722> (raw)
In-Reply-To: <5254A034.5020700@gmail.com>

On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
> Some setuid binaries will allow reading of files which have read
> permission by the real user id. This is problematic with files which
> use %pK because the file access permission is checked at open() time,
> but the kptr_restrict setting is checked at read() time. If a setuid
> binary opens a %pK file as an unprivileged user, and then elevates
> permissions before reading the file, then kernel pointer values may be
> leaked.

I think it should explicitly test 0.

Dan? Might this be any problem?

Otherwise, just style notes:

> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> @@ -1312,10 +1312,26 @@ char *pointer(const char *fmt, char *buf, char *end, void *ptr,
>  				spec.field_width = default_width;
>  			return string(buf, end, "pK-error", spec);
>  		}
> -		if (!((kptr_restrict == 0) ||
> -		      (kptr_restrict == 1 &&
> -		       has_capability_noaudit(current, CAP_SYSLOG))))
> -			ptr = NULL;
> +
> +		/*
> +		 * If kptr_restrict is set to 2, then %pK always prints as
> +		 * NULL. If it is set to 1, then only print the real pointer
> +		 * value if the current proccess has CAP_SYSLOG and is running
> +		 * with the same credentials it started with. This is because
> +		 * access to files is checked at open() time, but %pK checks
> +		 * permission at read() time. We don't want to leak pointer
> +		 * values if a binary opens a file using %pK and then elevates
> +		 * privileges before reading it.
> +		 */
> +		{
> +			const struct cred *cred = current_cred();

Please add #include <linux/cred.h>

> +			if (kptr_restrict == 2 || (kptr_restrict == 1 &&
> +			     (!has_capability_noaudit(current, CAP_SYSLOG) ||
> +			      !uid_eq(cred->euid, cred->uid) ||
> +			      !gid_eq(cred->egid, cred->gid))))
> +				ptr = NULL;
> +		}
>  		break;

Also, it might be easier to read as:

		if (kptr_restrict == 0)
			break;
		else if (kptr_restrict == 1) {
			const struct cred *cred = current_cred();

			if (!has_capability_noaudit(current, CAP_SYSLOG) ||
			    !uid_eq(cred->euid, cred->uid) ||
			    !gid_eq(cred->egid, cred->gid))
				ptr = NULL;
		} else {
			ptr = NULL;
		}
		break;

>  	case 'N':
>  		switch (fmt[1]) {



  reply	other threads:[~2013-10-09  0:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  0:15 Ryan Mallon
2013-10-09  0:49 ` Joe Perches [this message]
2013-10-09  1:30   ` Joe Perches
2013-10-09  1:55     ` Ryan Mallon
2013-10-09  2:00       ` Joe Perches
2013-10-09  2:22         ` Ryan Mallon
2013-10-09  2:30           ` Joe Perches
2013-10-09 11:14           ` Dan Rosenberg
2013-10-09 14:57             ` Joe Perches

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=1381279758.23937.42.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.rosenberg@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=eldad@fogrefinery.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jkosina@suse.cz \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=rmallon@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®