Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2023-40548

Publication date 23 January 2024

Last updated 24 July 2024


Ubuntu priority

Cvss 3 Severity Score

7.4 · High

Score breakdown

A buffer overflow was found in Shim in the 32-bit system. The overflow happens due to an addition operation involving a user-controlled value parsed from the PE binary being used by Shim. This value is further used for memory allocation operations, leading to a heap-based buffer overflow. This flaw causes memory corruption and can lead to a crash or data integrity issues during the boot phase.

Read the notes from the security team

Status

Package Ubuntu Release Status
secureboot-db 24.10 oracular
Not affected
24.04 LTS noble
Not affected
23.10 mantic
Not affected
23.04 lunar Ignored end of life, was needs-triage
22.04 LTS jammy
Not affected
20.04 LTS focal
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty
Not affected
shim 24.10 oracular
Fixed 15.8-0ubuntu1
24.04 LTS noble
Fixed 15.8-0ubuntu1
23.10 mantic Ignored end of life, was needed
23.04 lunar Ignored end of life, was needs-triage
22.04 LTS jammy
Vulnerable
20.04 LTS focal
Vulnerable
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial Ignored install media keys will never be revoked
14.04 LTS trusty Ignored install media keys will never be revoked
shim-signed 24.10 oracular
Fixed 1.58
24.04 LTS noble
Fixed 1.58
23.10 mantic Ignored end of life, was needed
23.04 lunar Ignored end of life, was needs-triage
22.04 LTS jammy
Vulnerable
20.04 LTS focal
Vulnerable
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial Ignored install media keys will never be revoked
14.04 LTS trusty Ignored install media keys will never be revoked

Notes


eslerm

UEFI Security Response Team states that dbx update is not needed secureboot-db should only ever be updated after shim secureboot-db is not updated on ESM releases as doing so would revoke install media keys Note that key revocation is required to protect against evil housekeeper attacks (such as BlackLotus)

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package Patch details
shim

Severity score breakdown

Parameter Value
Base score 7.4 · High
Attack vector Local
Attack complexity High
Privileges required None
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact High
Availability impact High
Vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H