{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-40271 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-40271 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-40271 is a high-severity vulnerability in n/a, published on 8 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-40271 and fix it if it is affected.\n\nWhat it is: CVE-2023-40271 is a high-severity vulnerability in n/a, published on 8 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-40271 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-40271/ (Markdown: https://insights.sbomify.com/CVE-2023-40271/index.md)","id":"CVE-2023-40271","markdown":"https://insights.sbomify.com/CVE-2023-40271/index.md","name":"CVE-2023-40271","record":{"aliases":["GHSA-7xgq-m8hq-839w"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Trusted Firmware-M","requires_auth":"none","summary":"Attackers can bypass authentication checks in CryptoCell accelerator implementations due to truncated tag comparison, allowing unauthenticated payloads to be accepted as valid.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trusted_firmware-m","vendor":"trustedfirmware"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2023-40271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Airflow Spark Provider Arbitrary File Read via JDBC","id":"CVE-2023-40272"},"packages":[],"prev":{"headline":"GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments","id":"CVE-2023-40267"},"products":["n/a"],"published":"2023-09-08","related":[{"cvss_score":5.5,"headline":"Arm Trusted Firmware Out-of-Bounds Write","id":"CVE-2021-27562","kev_date_added":"2021-11-03","published":"2021-05-25"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-43619","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-32032","kev_date_added":null,"published":"2021-05-21"},{"cvss_score":5.9,"headline":"Missing authorization in n/a","id":"CVE-2021-40327","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":4.7,"headline":"Information disclosure in n/a","id":"CVE-2023-51712","kev_date_added":null,"published":"2024-09-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["n/a"]},"summary":"Attackers can bypass authentication checks in CryptoCell accelerator implementations due to truncated tag comparison, allowing unauthenticated payloads to be accepted as valid.","url":"https://insights.sbomify.com/CVE-2023-40271/"}