CVE-2025-13912
BaseFortify
Publication date: 2025-12-11
Last updated on: 2025-12-11
Assigner: wolfSSL Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wolfssl | wolfssl | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-203 | The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves multiple constant-time implementations in wolfSSL before version 5.8.4 that may be transformed into non-constant-time binary code by LLVM compiler optimizations. This transformation can create observable timing discrepancies, which attackers can exploit through timing side-channel attacks to potentially disclose sensitive information.
How can this vulnerability impact me? :
The vulnerability can lead to information disclosure through timing side-channel attacks. This means that an attacker could potentially observe timing differences in cryptographic operations and use that information to extract sensitive data, compromising the confidentiality of communications or data protected by wolfSSL.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update wolfSSL to version 5.8.4 or later, which includes the security fix that prevents LLVM optimizations from breaking constant-time execution. This fix involves marking certain variables as volatile to maintain constant-time behavior and prevent timing side-channel attacks. Applying this update ensures cryptographic operations remain secure without performance impact. [1]