The BL1 FWU SMC handling code in ARM Trusted Firmware before 1.4 might allow attackers to write arbitrary data to secure memory, bypass the bl1_plat_mem_check protection mechanism, cause a denial of service, or possibly have unspecified other impact via a crafted AArch32 image, which triggers an integer overflow.
oryginał ENCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HTrustedfirmware Trusted Firmware A
OSTrustedfirmware≤ 1.3
Powiązane podatności
Trusted Firmware-A through 2.8 has an out-of-bounds read in the X.509 parser for parsing boot certificates. Th...
In all versions of ARM Trusted Firmware up to and including v1.4, not initializing or saving/restoring the PMC...
In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypas...
In ARM Trusted Firmware through 1.3, the secure self-hosted invasive debug interface allows normal world attac...
Improper input validation in ARM® Trusted Firmware used in AMD’s Zynq™ UltraScale+™) MPSoC/RFSoC may allow a p...