CVE-2024-32883: MCUboot Injection attack of unprotected TLV values
MCUboot is a secure bootloader for 32-bits microcontrollers. MCUboot uses a TLV (tag-length-value) structure to represent the meta data associated with an image. The TLVs themselves are divided into two sections, a protected and an unprotected section. The protected TLV entries are included as part of the image signature to avoid tampering. However, the code does not distinguish which TLV entries should be protected or not, so it is possible for an attacker to add unprotected TLV entries that should be protected. Currently, the primary protected TLV entries should be the dependency indication, and the boot record. An injected dependency value would primarily result in an otherwise acceptable image being rejected. A boot record injection could allow fields in a later attestation record to include data not intended, which could cause an image to appear to have properties that it should not have. As a workaround, disable the boot record functionality.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-32883?
CVE-2024-32883 has been classified with a high severity level due to its potential impact on the secure boot process.
How do I fix CVE-2024-32883?
To fix CVE-2024-32883, you should update to the latest version of MCUboot that addresses this vulnerability.
What version of MCUboot is affected by CVE-2024-32883?
CVE-2024-32883 affects all versions of MCUboot prior to the patched release that mitigates this vulnerability.
What impact does CVE-2024-32883 have on MCUboot users?
The impact of CVE-2024-32883 includes potential unauthorized access to the firmware and compromise of the secure boot process.
Is there an official advisory for CVE-2024-32883?
Yes, there is an official advisory available detailing CVE-2024-32883 and its implications on the MCUboot project.