Vulnerabilities > ARM > Trusted Firmware M
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-09-05 | CVE-2023-51712 | Unspecified vulnerability in ARM Trusted Firmware-M An issue was discovered in Trusted Firmware-M through 2.0.0. high complexity arm | 4.7 |
2023-09-08 | CVE-2023-40271 | Incorrect Comparison vulnerability in ARM Trusted Firmware-M In Trusted Firmware-M through TF-Mv1.8.0, for platforms that integrate the CryptoCell accelerator, when the CryptoCell PSA Driver software Interface is selected, and the Authenticated Encryption with Associated Data Chacha20-Poly1305 algorithm is used, with the single-part verification function (defined during the build-time configuration phase) implemented with a dedicated function (i.e., not relying on usage of multipart functions), the buffer comparison during the verification of the authentication tag does not happen on the full 16 bytes but just on the first 4 bytes, thus leading to the possibility that unauthenticated payloads might be identified as authentic. | 7.5 |
2022-03-01 | CVE-2021-43619 | Classic Buffer Overflow vulnerability in ARM Trusted Firmware-M 1.4.0/1.4.1 Trusted Firmware M 1.4.x through 1.4.1 has a buffer overflow issue in the Firmware Update partition. | 7.8 |
2021-05-25 | CVE-2021-27562 | Out-of-bounds Write vulnerability in ARM Trusted Firmware M 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 secure functions under the NSPE handler mode. | 5.5 |