CVE-2025-7396
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-18

Last updated on: 2025-12-03

Assigner: wolfSSL Inc.

Description
In wolfSSL release 5.8.2 blinding support is turned on by default for Curve25519 in applicable builds. The blinding configure option is only for the base C implementation of Curve25519. It is not needed, or available with; ARM assembly builds, Intel assembly builds, and the small Curve25519 feature. While the side-channel attack on extracting a private key would be very difficult to execute in practice, enabling blinding provides an additional layer of protection for devices that may be more susceptible to physical access or side-channel observation.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-18
Last Modified
2025-12-03
Generated
2026-05-06
AI Q&A
2025-07-19
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wolfssl wolfssl 5.8.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-385 Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability relates to the blinding support for Curve25519 in wolfSSL release 5.8.2. Blinding is a security feature intended to protect against side-channel attacks that could extract private keys. In this release, blinding is enabled by default only for the base C implementation of Curve25519, but it is not available or needed for ARM assembly builds, Intel assembly builds, or the small Curve25519 feature. Although side-channel attacks to extract private keys are very difficult to execute in practice, enabling blinding adds an extra layer of protection for devices that might be more vulnerable to physical access or side-channel observation.


How can this vulnerability impact me? :

If an attacker were able to perform a side-channel attack on a device using wolfSSL's Curve25519 implementation without blinding, they might extract private keys, compromising the security of cryptographic operations. However, since blinding is enabled by default for the base C implementation, this risk is mitigated for most builds. Devices using ARM or Intel assembly builds or the small Curve25519 feature do not have blinding enabled, which could make them more susceptible if physical access or side-channel observation is possible. Overall, the impact is a potential risk of private key exposure through side-channel attacks, but the difficulty of such attacks and the default blinding reduce this risk.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, ensure that blinding support for Curve25519 is enabled in your wolfSSL implementation, especially if you are using the base C implementation. Avoid using builds without blinding support such as ARM assembly builds, Intel assembly builds, or the small Curve25519 feature if you require this protection. Enabling blinding provides an additional layer of protection against side-channel attacks.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart