Potential non-constant time compiled code with Clang LLVM
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 | wolfSSL | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Wolfssl | Wolfssl | — |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.158% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/9148 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wolfssl
Wolfssl wolfssl |
|
| Vendors & Products |
Wolfssl
Wolfssl wolfssl |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks. | |
| Title | Potential non-constant time compiled code with Clang LLVM | |
| Weaknesses | CWE-203 | |
| References |
| |
| Metrics |
cvssV4_0
|