Read the docs

Out-of-bounds read in MCUboot image hash during validation

Priority LOW 13CWE-125Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

MCUboot from 1.6.0 before 2.5.0 hashes an image span whose sizes come from the candidate image header without checking that the span fits in the flash area. An attacker who can place an image in a slot, through an application-delivered update or serial recovery, can make image validation read past the end of the area (CWE-125). The bytes read are used only for the digest and are never returned, so the realistic effect is a read fault during validation on backends that do not bounds-check reads.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

bootutil_img_hash() computes the image digest over ih_hdr_size + ih_img_size + ih_protect_tlv_size bytes, all three taken from the candidate image's header, and reads that span out of the slot without checking that it fits in the flash area. The three sizes are also summed without an overflow check. Nothing earlier on the validation path bounds the whole span either: bootutil_img_validate() compares the image size against bootutil_max_image_size() only after the hash has been computed. The callers bound part of the span, or none of it: On the swap and overwrite upgrade path, boot_validate_slot() first runs the image header check (boot_is_header_valid(), later boot_check_header_valid()). Before MCUboot 2.2.0 that check covered only ih_hdr_size + ih_img_size, so for every image the protected-TLV area (ih_protect_tlv_size, a uint16_t, up to 65535 bytes) was hashed without being bounded. From 2.2.0 the check includes ih_protect_tlv_size, except for a compressed image in the secondary slot when MCUBOOT_DECOMPRESS_IMAGES (CONFIG_BOOT_DECOMPRESSION) is enabled, which leaves the same gap of up to 64 KB. Zephyr's single-slot and firmware loaders (boot/zephyr/single_loader.c, boot/zephyr/firmware_loader.c) read the header with boot_image_load_header(), which bounds ih_hdr_size + ih_img_size against the flash area. Before MCUboot 2.4.0 that bound did not include ih_protect_tlv_size, which leaves the same gap of up to 64 KB. From 2.4.0 these loaders bound the whole span. The serial recovery image-list and image-state handlers (bs_list() and bs_set() in boot/boot_serial/src/boot_serial.c) call bootutil_img_validate() with no header check at all, so on those paths ih_img_size is unbounded as well. The image is hashed before its signature is checked, so anyone who can place an image in a slot (an OTA or SMP update delivered through the application, or serial recovery) reaches this read before authentication. Whether a malformed header produces an actual read beyond the area depends on the flash backend: Backends whose flash_area_read() bounds-checks the request (Zephyr, Espressif, NuttX, Mbed) return an error once the chunked read crosses the end of the area. Validation fails and the image is rejected, with no over-read. With MCUBOOT_HASH_STORAGE_DIRECTLY (Zephyr CONFIG_BOOT_IMG_HASH_DIRECTLY_ON_STORAGE, available from 2.2.0, not enabled by default) the span is hashed through a single direct pointer into memory-mapped flash, with no bounds check. The Cypress PSoC6 port's flash_area_read() (boot/cypress/cy_flash_pal/cy_flash_map.c, from 1.6.0) does not bound the read: its assert()s compare against the area's absolute offset rather than its size, and it copies with memcpy(). The bytes read past the area feed only the digest, which is compared internally and never returned, so nothing is disclosed. The realistic effect is a read fault during image validation: up to 64 KB past the slot on the upgrade path and, before 2.4.0, on the Zephyr loaders, and potentially much further on the serial recovery handlers, which skip the header check. Where validation is repeated at every boot (a pending upgrade, or, before 2.4.0, the single-slot loader checking its image), the fault can recur on each reset and keep the device from booting. The fix makes bootutil_img_hash() add the three sizes with boot_u32_safe_add() and reject an image whose span, including the sector offset used in swap-using-offset mode, does not fit in the flash area, before any of it is hashed. Because the bound is applied where the bytes are read, it covers every caller.

Why it matters now

EPSS 0.00115 1st percentileScored 2026-11-16
Fix Fixed mcuboot (mcu-tools): 2.5.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
mcu-toolsmcuboot1.6.0 to before 2.5.02.5.0Patch availableCNA
  • mcuboot Vendormcu-tools Affected 1.6.0 to before 2.5.0 Fixed in 2.5.0 Patch available CNA

Remediation

Update mcuboot to version 2.5.0 or later, which fixes this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA mcuboot (mcu-tools) Fixed in 2.5.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    mcu-tools mcuboot 2.5.0

    7 records Highest priority Priority LOW 7 LOW

    Other records, highest priority first

    • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image uploadPriority LOW 17
    • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512Priority LOW 13
    • TI-2026-91072 Uninitialised stack memory leaks into MCUboot measured-boot recordPriority LOW 11

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127916

References

  • TI-2024-21755 MCUboot Injection attack of unprotected TLV values CVSS 3.1HIGH 7.7
  • TI-2026-91073 Out-of-bounds read in MCUboot serial recovery image index CVSS 3.1MEDIUM 5.1
  • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image upload CVSS 3.1MEDIUM 4.0
  • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512 CVSS 3.1LOW 2.9
  • TI-2026-91072 Uninitialised stack memory leaks into MCUboot measured-boot record CVSS 3.1LOW 2.4
  • TI-2026-91077 MCUboot TLV iterator reads entries without bounds check against TLV area CVSS 3.1LOW 2.0
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences