An insecure default to allow UEFI Shell in EDK2 was left enabled in Ubuntus EDK2. This allows an OS-resident attacker to bypass Secure Boot.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Lxd | Canonical | 5.0-candidate (including) | 5.0-candidate (including) |
| Lxd | Canonical | 5.21-candidate (including) | 5.21-candidate (including) |
| Lxd | Canonical | 5.21-edge (including) | 5.21-edge (including) |
| Edk2 | Tianocore | * | 2023.11-8 (including) |
| Edk2 | Ubuntu | bionic | * |
| Edk2 | Ubuntu | devel | * |
| Edk2 | Ubuntu | esm-infra/focal | * |
| Edk2 | Ubuntu | focal | * |
| Edk2 | Ubuntu | jammy | * |
| Edk2 | Ubuntu | lunar | * |
| Edk2 | Ubuntu | mantic | * |
| Edk2 | Ubuntu | noble | * |
| Edk2 | Ubuntu | oracular | * |
| Edk2 | Ubuntu | plucky | * |
| Edk2 | Ubuntu | trusty | * |
| Edk2 | Ubuntu | xenial | * |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.