From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 47185@debbugs.gnu.org
Subject: bug#47185: grub2 package is vulnerable to CVE-2020-14372, CVE-2020-25632, CVE-2020-25647, CVE-2020-27749, CVE-2020-27779, CVE-2021-20225, CVE-2021-20233 and CVE-2021-3418
Date: Tue, 16 Mar 2021 09:08:31 +0100 [thread overview]
Message-ID: <ba69ba4020b40dfa182174ea2395cf17195512d5.camel@zaclys.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
As outlined by
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass2021
we have a new wave of GRUB security vulnerabilities around SecureBoot.
There is no new upstream release so patching this appears to be some
kind of sport.
Debian has patched it in this commit:
https://salsa.debian.org/grub-team/grub/-/commit/37c2a594625efba8b7f10d18a444393982d2e31f
I see also there's a new concept of SBAT section to ease administrative
efforts around certificate revocation when signed binaries such as some
GRUB2 things become vulnerable (and we don't want them to verify
successfully anymore).
This looks like a sizeable upgrade to a sensitive part of GNU Guix, so
we have to test carefully.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-03-16 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:08 Léo Le Bouter via Bug reports for GNU Guix [this message]
2021-03-16 8:16 ` bug#47185: grub2 package is vulnerable to CVE-2020-14372, CVE-2020-25632, CVE-2020-25647, CVE-2020-27749, CVE-2020-27779, CVE-2021-20225, CVE-2021-20233 and CVE-2021-3418 Léo Le Bouter via Bug reports for GNU Guix
2021-03-16 8:36 ` Léo Le Bouter via Bug reports for GNU Guix
2021-03-16 23:47 ` Mark H Weaver
2021-03-17 2:15 ` Leo Famulari
[not found] <35e9d8fb5e5caacb8abac2ead7742d7ccd9ee737.camel@zaclys.net>
2022-03-23 3:32 ` Maxim Cournoyer
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=ba69ba4020b40dfa182174ea2395cf17195512d5.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47185@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.