Payload authentication bypass via four-byte tag comparison
Published Sep 8, 2023 · Updated Sep 26, 2024
Incorrect tag verification in Trusted Firmware-M 1.6.0 through 1.8.0 allows attackers to pass unauthenticated payloads as authentic via network input. In cc3xx_decrypt_chacha20_poly1305(), the comparison loop uses sizeof(tag_length), checking four bytes rather than the full 16-byte tag length. Reachability requires a CC312-enabled build with the legacy driver disabled and the dedicated single-part ChaCha20-Poly1305 path enabled.
Summary
What happened
Incorrect tag verification in Trusted Firmware-M 1.6.0 through 1.8.0 allows attackers to pass unauthenticated payloads as authentic via network input. In cc3xx_decrypt_chacha20_poly1305(), the comparison loop uses sizeof(tag_length), checking four bytes rather than the full 16-byte tag length. Reachability requires a CC312-enabled build with the legacy driver disabled and the dedicated single-part ChaCha20-Poly1305 path enabled.
The record
- CVE
- CVE-2023-40271
- Published
- Sep 8, 2023
- Updated
- Sep 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-697
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo