ARM Trusted Firmware-M 1.6.1
Approved changes feed: RSS · Atom
cpe:2.3:o:arm:trusted_firmware-m:1.6.1:*:*:*:*:*:*:*
part: o version: 1.6.1 update: *
| Vendor | Arm (992f6a5c-1bc7-5785-a659-421ca2a38af9) |
|---|---|
| Product | Trusted Firmware M (02507aac-424e-5422-9348-9db3833f2def) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-40271 |
vulnerable | 2026-06-08 06:09:41.924748 |
Details available
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.
Published: 2023-09-08T00:00:00.000Z
Updated: 2024-09-26T17:53:51.455Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.