Trustedfirmware
Trustedfirmware Trusted Firmware-a: vulnerabilidades y CVE
Trustedfirmware Trusted Firmware-a tiene 7 vulnerabilidades publicadas, 0 de ellas en los últimos 12 meses. 0 son críticas y 0 figuran en el catálogo de explotación activa de CISA.
CVE7
Últimos 12 meses0
Críticas0
Explotadas activamente0
Todas las vulnerabilidades en el catálogo →⭐ Seguir esta tecnología
Últimas vulnerabilidades
| CVE | Severidad | EPSS | Explotación activa | Publicada | Descripción |
|---|---|---|---|---|---|
| CVE-2023-31339 | Media (5.8) | 0.16% | — | 13 ago 2024 | 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. |
| CVE-2022-47630 | Alta (7.4) | 0.63% | — | 16 ene 2023 | 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… |
| CVE-2018-19440 | Media (5.3) | 1.4% | — | 30 ene 2019 | ARM Trusted Firmware-A allows information disclosure. |
| CVE-2017-15031 | Alta (7.5) | 1.9% | — | 18 dic 2018 | 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. |
| CVE-2017-9607 | Alta (7) | 0.79% | — | 20 sept 2017 | 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… |
| CVE-2017-7564 | Alta (7.5) | 1.0% | — | 7 jun 2017 | 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… |
| CVE-2017-7563 | Alta (8.1) | 0.89% | — | 7 jun 2017 | 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… |