AES-256-GCM Authentication Tag Does Not Cover First Ciphertext Blocks When AAD Is Empty
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Caliptra | Core Runtime Firmware | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Caliptra | Core Runtime Firmware |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.197% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Caliptra
Caliptra core Runtime Firmware |
|
| Vendors & Products |
Caliptra
Caliptra core Runtime Firmware |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Missing cryptographic step in Caliptra Core Firmware (aes_256_gcm_update module) results in an incorrect GCM authentication tag. When the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not saved after the first update call, causing the final tag to exclude the first batch of processed ciphertext. Ciphertext produced by that call may be modified without the tag reflecting the change. This issue affects Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0. | |
| Title | AES-256-GCM Authentication Tag Does Not Cover First Ciphertext Blocks When AAD Is Empty | |
| Weaknesses | CWE-325 | |
| References |
| |
| Metrics |
cvssV4_0
|