Trustedfirmware Trusted_firmware-a
7 CVEs affecting Trustedfirmware Trusted_firmware-a. Latest disclosed: 2024-08-13. Critical: 0, High: 5.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2017-7563 | High | 8.1 | 2017-06-07 | 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… |
CVE-2017-15031 | High | 7.5 | 2018-12-18 | 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 infor… |
CVE-2017-7564 | High | 7.5 | 2017-06-07 | 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 p… |
CVE-2022-47630 | High | 7.4 | 2023-01-16 | 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_nvc… |
CVE-2017-9607 | High | 7.0 | 2017-09-20 | 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… |
CVE-2018-19440 | Medium | 5.3 | 2019-01-30 | ARM Trusted Firmware-A allows information disclosure. |
CVE-2023-31339 | Medium | 4.8 | 2024-08-13 | 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… |