linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Kees Cook <keescook@chromium.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Laurent Vivier <laurent@vivier.eu>,
	YunQiang Su <ysu@wavecomp.com>, Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] exec: Make suid_dumpable apply to SUID/SGID binaries irrespective of invoking users
Date: Tue, 21 Dec 2021 11:41:27 -0500	[thread overview]
Message-ID: <4f67dc4c-7038-7dde-cad9-4feeaa6bc71b@redhat.com> (raw)
In-Reply-To: <87lf0e7y0k.fsf@email.froward.int.ebiederm.org>


On 12/21/21 10:55, Eric W. Biederman wrote:
> Waiman Long <longman@redhat.com> writes:
>
>> The begin_new_exec() function checks for SUID or SGID binaries by
>> comparing effective uid and gid against real uid and gid and using
>> the suid_dumpable sysctl parameter setting only if either one of them
>> differs.
>>
>> In the special case that the uid and/or gid of the SUID/SGID binaries
>> matches the id's of the user invoking it, the suid_dumpable is not
>> used and SUID_DUMP_USER will be used instead. The documentation for the
>> suid_dumpable sysctl parameter does not include that exception and so
>> this will be an undocumented behavior.
>>
>> Eliminate this undocumented behavior by adding a flag in the linux_binprm
>> structure to designate a SUID/SGID binary and use it for determining
>> if the suid_dumpable setting should be applied or not.
> I see that you are making the code match the documentation.
> What harm/problems does this mismatch cause in practice?
> What is the motivation for this change?
>
> I am trying to see the motivation but all I can see is that
> in the case where suid and sgid do nothing in practice the code
> does not change dumpable.  The point of dumpable is to refuse to
> core dump when it is not safe.  In this case since nothing happened
> in practice it is safe.
>
> So how does this matter in practice.  If there isn't a good
> motivation my feel is that it is the documentation that needs to be
> updated rather than the code.
>
> There are a lot of warts to the suid/sgid handling during exec.  This
> just doesn't look like one of them

This patch is a minor mitigation in response to the security 
vulnerability as posted in 
https://www.openwall.com/lists/oss-security/2021/10/20/2 (aka 
CVE-2021-3864). In particular, the Su PoC (tested on CentOS 7) showing 
that the su invokes /usr/sbin/unix_chkpwd which is also a SUID binary. 
The initial su invocation won't generate a core dump because the real 
uid and euid differs, but the second unix_chkpwd invocation will. This 
patch eliminates this hole by making sure that all SUID binaries follow 
suid_dumpable setting.

Cheers,
Longman



  reply	other threads:[~2021-12-21 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  2:17 [PATCH] exec: Make suid_dumpable apply to SUID/SGID binaries irrespective of invoking users Waiman Long
2021-12-21 15:55 ` Eric W. Biederman
2021-12-21 16:41   ` Waiman Long [this message]
2021-12-21 17:35     ` Eric W. Biederman
2021-12-21 18:01       ` Waiman Long
2021-12-21 18:19         ` Linus Torvalds
2021-12-21 19:27           ` Waiman Long
2021-12-21 20:56             ` Willy Tarreau
2021-12-21 22:13               ` Willy Tarreau
2021-12-21 23:35                 ` Eric W. Biederman
2021-12-22  6:29                   ` Willy Tarreau
2021-12-26 15:03                   ` Willy Tarreau

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=4f67dc4c-7038-7dde-cad9-4feeaa6bc71b@redhat.com \
    --to=longman@redhat.com \
    --cc=deller@gmx.de \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=laurent@vivier.eu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ysu@wavecomp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).