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. This affects TF-Mv1.6.0, TF-Mv1.6.1, TF-Mv1.7.0, and TF-Mv1.8.
The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Trusted_firmware-m | Arm | 1.6.0 (including) | 1.6.0 (including) |
| Trusted_firmware-m | Arm | 1.6.1 (including) | 1.6.1 (including) |
| Trusted_firmware-m | Arm | 1.7.0 (including) | 1.7.0 (including) |
| Trusted_firmware-m | Arm | 1.8.0 (including) | 1.8.0 (including) |
This Pillar covers several possibilities: