wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| wolfSSL Inc. | wolfProvider | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wolfssl | Wolfprovider |
|
Vendor Solution
Upgrade to wolfProvider 1.2.2, which increments the explicit nonce after each record. As an interim mitigation use AES-CCM or TLS 1.3 instead of TLS 1.2 / DTLS 1.2 AES-GCM.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.383% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.wolfssl.com/docs/security-vulnerabilities/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wolfssl:wolfprovider:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wolfssl
Wolfssl wolfprovider |
|
| Vendors & Products |
Wolfssl
Wolfssl wolfprovider |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | wolfProvider before 1.2.2 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce discloses the keystream (the XOR of two ciphertexts equals the XOR of their plaintexts, so one known record recovers the others) and leaks the GHASH authentication key, enabling authentication tag forgery. AES-CCM, TLS 1.3, and non-TLS use of the cipher are not affected. | |
| Title | wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record | |
| Weaknesses | CWE-323 | |
| References |
| |
| Metrics |
cvssV3_1
|