unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: guix-devel@gnu.org, guix-security@gnu.org
Subject: Is Guix vulnerable to this polkit CVE?
Date: Thu, 10 Jun 2021 22:35:02 +0000	[thread overview]
Message-ID: <fec72ae9477f1606cbec32d8cf532044@dismail.de> (raw)

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

I just found this article on polkit having a CVE:

https://github.blog/2021-06-10-privilege-escalation-polkit-root-on-linux-with-bug/ (https://github.blog/2021-06-10-privilege-escalation-polkit-root-on-linux-with-bug/)
It looks pretty nasty...

" The vulnerability enables an unprivileged local user to get a root shell on the system. It’s easy to exploit with a few standard command line tools, as you can see in this short video (https://youtu.be/QZhz64yEd0g). In this blog post, I’ll explain how the exploit works and show you where the bug was in the source code. "
In the hacker news comments it is fixed in:
https://news.ycombinator.com/item?id=27462247 (https://news.ycombinator.com/item?id=27462247)

Polkit version 0.119 fixes it, here's the diff: https://gitlab.freedesktop.org/polkit/polkit/-/commit/a04d13... (https://gitlab.freedesktop.org/polkit/polkit/-/commit/a04d13affe0fa53ff618e07aa8f57f4c0e3b9b81)
You all awesome devs have probably already fixed it, but I am just emailing to make sure.

Thanks!

Joshua

"Aim for stars...because even if you'll fall at least you'll fall on Uranus."

[-- Attachment #2: Type: text/html, Size: 1570 bytes --]

             reply	other threads:[~2021-06-10 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 22:35 jbranso [this message]
2021-06-10 22:56 ` Is Guix vulnerable to this polkit CVE? Tobias Geerinckx-Rice
  -- strict thread matches above, loose matches on Subject: below --
2021-06-10 23:00 Leo Prikler

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=fec72ae9477f1606cbec32d8cf532044@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=guix-security@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).