Trustedfirmware Trusted_firmware-m
8 CVEs affecting Trustedfirmware Trusted_firmware-m. Latest disclosed: 2024-09-05. 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-2021-43619 | High | 7.8 | 2022-03-01 | Trusted Firmware M 1.4.x through 1.4.1 has a buffer overflow issue in the Firmware Update partition. In the IPC model, a psa_fwu_write caller from SPE or NSPE… |
CVE-2023-40271 | High | 7.5 | 2023-09-08 | In Trusted Firmware-M through TF-Mv1.8.0, for platforms that integrate the CryptoCell accelerator, when the CryptoCell PSA Driver software Interface is selecte… |
CVE-2021-32032 | High | 7.5 | 2021-05-21 | In Trusted Firmware-M through 1.3.0, cleaning up the memory allocated for a multi-part cryptographic operation (in the event of a failure) can prevent the abor… |
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-2021-40327 | Medium | 5.9 | 2022-01-13 | Trusted Firmware-M (TF-M) 1.4.0, when Profile Small is used, has incorrect access control. NSPE can access a secure key (held by the Crypto service) based sole… |
CVE-2021-27562 | Medium | 5.5 | 2021-05-25 | In Arm Trusted Firmware M through 1.2, the NS world may trigger a system halt, an overwrite of secure data, or the printing out of secure data when calling sec… |
CVE-2023-51712 | Medium | 4.7 | 2024-09-05 | An issue was discovered in Trusted Firmware-M through 2.0.0. The lack of argument verification in the logging subsystem allows attackers to read sensitive data… |