Vulnerabilidad · Publicado 07/09/2026
MCUboot en configuración base no verifica adecuadamente la integridad de imágenes al usar la estrategia Direct XIP, permitiendo que la imagen principal inicie núcleos secundarios (radio, etc.) desde slots sin validar. Esto afecta sistemas embebidos y dispositivos IoT en operaciones altas de LATAM, especialmente en telecomunicaciones e industria.
When using the Direct XIP update strategy, the main application image starts other cores (i.e. radio core), based on the currently active slot without additional verification. The MCUboot in the bare (upstream) configuration assumes that if there is at least a single slot for each image available, the system is bootable and continues the boot process. This may lead to a situation when MCUboot picks different slot for different images (i.e. (a) for the main application and (b) for the radio image), boots the main application (from slot (a)) that afterwards starts the radio image by providing an address of the unauthenticated slot ((a) instead of (b)).
Score: 7.5/10 — Severidad: HIGH — Estado NIST: Received
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE-347
Publicado en NIST NVD.