[Bug 1890835] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for secureboot-db has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to secureboot-db in Ubuntu.
https://bugs.launchpad.net/bugs/1890835

Title:
  secureboot-db 2020 update

Status in secureboot-db package in Ubuntu:
  Fix Released
Status in secureboot-db source package in Trusty:
  New
Status in secureboot-db source package in Xenial:
  Fix Committed
Status in secureboot-db source package in Bionic:
  Fix Committed
Status in secureboot-db source package in Focal:
  Fix Released
Status in secureboot-db source package in Groovy:
  Fix Released

Bug description:
  NB! do not release this update to -updates, until slow phasing is
  available, at 4% per day.

  NB! ideally phase one series at the time, to ensure we can deal with a
  flood of support requests if any arise.

  [Impact]

   * Ship 2020 dbxupdate from MS

  [Test Case]

   * In case of multi-boot systems, please plan to boot into every
  operating system on your multi-boot systems and install updates as
  soon as your other operating system distributions publish updates for
  BootHole vulnerability.

   * Install package on Secureboot UEFI enabled system
   * Reboot
   * Observe that it still reboots

  [Regression Potential]

   * Installing this package even once will update DBX variable in the
  UEFI firmware and will prevent booting:

   - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones / media released before August 2020
   - Certain version of Kaspersky Labs UEFI protect software
   - Certain version of HPE Inc ProLiant automatic OS provisioning

  As they are all vulnerable to the BootHole vunlerability.

  For example, one will have to use 16.04.7 LTS, 18.04.5 LTS, 20.04.1
  LTS installer media if they want to reinstall.

  If any dual boot configurations are failing to boot, one must
  navigated to UEFI BIOS settings and either reset DBX variables to
  stock values, or disable secureboot. Upgrade any systems that are now
  prohibited to boot. And then re-enable secureboot & reinstall
  secureboot-db package to reapply dbx updates.

  Please note simple downgrade of secureboot-db package will not achieve
  anything, as downgrading the package does not revert the firmware
  changes.

  [Other Info]

   * For more inforamtion please see
  https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+subscriptions