CVE-2022-25640
First published: Thu Feb 24 2022(Updated: )
In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly enforce a requirement for mutual authentication. A client can simply omit the certificate_verify message from the handshake, and never present a certificate.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WolfSSL wolfssl | <5.2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2022-25640.
What is the severity of CVE-2022-25640?
The severity of CVE-2022-25640 is high, with a severity value of 7.5.
How does CVE-2022-25640 affect wolfSSL?
CVE-2022-25640 affects wolfSSL versions up to and excluding 5.2.0.
What is the impact of CVE-2022-25640?
The impact of CVE-2022-25640 is that a TLS 1.3 server using wolfSSL may not be able to enforce mutual authentication properly.
Is there a fix available for CVE-2022-25640?
Yes, the fix for CVE-2022-25640 can be found in wolfSSL version 5.2.0 and later.
- agent/type
- agent/author
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/wolfssl
- canonical/wolfssl wolfssl