Vulnerability Description
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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/mcu-tools/mcuboot/security/advisories/GHSA-m59c-q9gq-rh2j
- https://github.com/mcu-tools/mcuboot/security/advisories/GHSA-m59c-q9gq-rh2j
FAQ
What is CVE-2024-32883?
CVE-2024-32883 is a vulnerability with a CVSS score of 7.7 (HIGH). 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 ...
How severe is CVE-2024-32883?
CVE-2024-32883 has been rated HIGH with a CVSS base score of 7.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-32883?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.