{"dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": {"state": "PUBLISHED", "cveId": "CVE-2023-40271", "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "assignerShortName": "mitre", "dateUpdated": "2024-08-02T18:31:52.418Z", "dateReserved": "2023-08-11T00:00:00", "datePublished": "2023-09-08T00:00:00"}, "containers": {"cna": {"providerMetadata": {"orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "shortName": "mitre", "dateUpdated": "2023-09-08T01:59:45.526188"}, "descriptions": [{"lang": "en", "value": "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."}], "affected": [{"vendor": "n/a", "product": "n/a", "versions": [{"version": "n/a", "status": "affected"}]}], "references": [{"url": "https://tf-m-user-guide.trustedfirmware.org/releases/index.html"}, {"url": "https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/security/security_advisories/cc3xx_partial_tag_compare_on_chacha20_poly1305.rst"}], "problemTypes": [{"descriptions": [{"type": "text", "lang": "en", "description": "n/a"}]}]}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-02T18:31:52.418Z"}, "title": "CVE Program Container", "references": [{"url": "https://tf-m-user-guide.trustedfirmware.org/releases/index.html", "tags": ["x_transferred"]}, {"url": "https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/security/security_advisories/cc3xx_partial_tag_compare_on_chacha20_poly1305.rst", "tags": ["x_transferred"]}]}]}}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:arm:trusted_firmware-m:1.6.0:*:*:*:*:*:*:*", "matchCriteriaId": "9F60A1CE-5C19-4996-BA41-E56EA2C1916C", "vulnerable": true}, {"criteria": "cpe:2.3:a:arm:trusted_firmware-m:1.6.1:*:*:*:*:*:*:*", "matchCriteriaId": "CD608A87-1120-4D73-9449-36510BB33A6B", "vulnerable": true}, {"criteria": "cpe:2.3:a:arm:trusted_firmware-m:1.7.0:*:*:*:*:*:*:*", "matchCriteriaId": "A3BAE3BF-5B14-4348-A91A-1556067425E7", "vulnerable": true}, {"criteria": "cpe:2.3:a:arm:trusted_firmware-m:1.8.0:*:*:*:*:*:*:*", "matchCriteriaId": "947E609C-2B59-4114-ACBE-ED3ECEC61D34", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "En Trusted Firmware-M hasta TF-Mv1.8.0, para plataformas que integran el acelerador CryptoCell, cuando se selecciona la Interfaz del software CryptoCell PSA Driver y se utiliza el algoritmo Cifrado Autenticado con Datos Asociados Chacha20-Poly1305, con la verificaci\u00f3n de una funci\u00f3n single-part (definida durante la fase de configuraci\u00f3n en tiempo de compilaci\u00f3n) implementada con una funci\u00f3n dedicada (es decir, que no depende del uso de funciones multipart), la comparaci\u00f3n del b\u00fafer de meoria durante la verificaci\u00f3n de la etiqueta de autenticaci\u00f3n no ocurre en los 16 bytes completos sino solo en los primeros 4 bytes, lo que genera la posibilidad de que los payloads no autenticados puedan identificarse como aut\u00e9nticas. Esto afecta a TF-Mv1.6.0, TF-Mv1.6.1, TF-Mv1.7.0 y TF-Mv1.8."}], "id": "CVE-2023-40271", "lastModified": "2023-09-13T02:27:16.427", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2023-09-08T02:15:08.133", "references": [{"source": "cve@mitre.org", "tags": ["Exploit", "Mitigation", "Technical Description", "Vendor Advisory"], "url": "https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/security/security_advisories/cc3xx_partial_tag_compare_on_chacha20_poly1305.rst"}, {"source": "cve@mitre.org", "tags": ["Release Notes"], "url": "https://tf-m-user-guide.trustedfirmware.org/releases/index.html"}], "sourceIdentifier": "cve@mitre.org", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-697"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{}