public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>, cip-dev@lists.cip-project.org
Subject: Re: pkexec vs kernel -- root to anyone who asks nicely
Date: Tue, 7 Jun 2022 10:20:46 +0200	[thread overview]
Message-ID: <20220607082046.GA23037@duo.ucw.cz> (raw)
In-Reply-To: <8a6279d1-a02f-8808-de08-c2c195d36969@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

Hi!

> > There's a security problem in pkexec vs. kernel interaction. Impact is
> > local root. If you want to get root on someone else's system, it
> > should be easy right now. It is fixed in 5.18, 5.10.120, and latest
> > 4.9 and 4.19 kernels.
> > 
> > Do you have untrusted users on your system and you need pkexec?
> > 
> 
> Is that https://nvd.nist.gov/vuln/detail/cve-2021-4034, and does that
> relate to "This vulnerability has been modified and is currently
> undergoing reanalysis."? Or is it something else?

Yes, it is same thing... see dcd46d897adb70d63e025f175a00a89797d31a43
and https://www.qualys.com/2022/01/25/cve-2021-4034/pwnkit.txt .

Pkexec is gnome-related, so should not be too usual on embedded
systems, and you should not really have untrusted users on your
embedded system, either.

But if someone has them and is using pkexec, we may need to do extra
updates.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2022-06-07  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 17:57 pkexec vs kernel -- root to anyone who asks nicely Pavel Machek
2022-06-07  7:20 ` Jan Kiszka
2022-06-07  8:20   ` Pavel Machek [this message]

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=20220607082046.GA23037@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.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