Trusted Firmware A vulnerabilities

7 vulnerabilities

Known vulnerabilities in Trusted Firmware A, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

5.3CVE-2018-19440debianarm-trusted-firmware+2
EPSS score
1.44%
ARM Trusted Firmware-A allows information disclosure.7.4CVE-2022-47630debianarm-trusted-firmware+2
EPSS score
0.63%
Trusted Firmware-A through 2.8 has an out-of-bounds read in the X.509 parser for parsing boot certificates. This affects downstream use of get_ext and auth_nvctr. Attackers might be able to trigger dangerous read side effects or obtain sensitive information about microarchitectural state.7CVE-2017-9607trustedfirmwaretrusted_firmware-a
EPSS score
0.79%
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.7.5CVE-2017-7564trustedfirmwaretrusted_firmware-a
EPSS score
1.05%
In ARM Trusted Firmware through 1.3, the secure self-hosted invasive debug interface allows normal world attackers to cause a denial of service (secure world panic) via vectors involving debug exceptions and debug registers.8.1CVE-2017-7563trustedfirmwaretrusted_firmware-a
EPSS score
0.89%
In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypass the MT_EXECUTE_NEVER protection mechanism. This issue occurs because of inconsistency in the number of execute-never bits (one bit versus two bits).7.5CVE-2017-15031debianarm-trusted-firmware+1
EPSS score
1.90%
In all versions of ARM Trusted Firmware up to and including v1.4, not initializing or saving/restoring the PMCR_EL0 register can leak secure world timing information.5.8CVE-2023-31339amdtrusted_firmware-a+2
EPSS score
0.16%
Improper input validation in ARM® Trusted Firmware used in AMD’s Zynq™ UltraScale+™) MPSoC/RFSoC may allow a privileged attacker to perform out of bound reads, potentially resulting in data leakage and denial of service.