CVE-2020-24613
First published: Mon Aug 24 2020(Updated: )
wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the WAIT_CERT_CR state, within SanityCheckTls13MsgReceived() in tls13.c. This is an incorrect implementation of the TLS 1.3 client state machine. This allows attackers in a privileged network position to completely impersonate any TLS 1.3 servers, and read or modify potentially sensitive information between clients using the wolfSSL library and these TLS servers.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WolfSSL wolfssl | <4.5.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 CVE-2020-24613?
CVE-2020-24613 refers to a vulnerability in wolfSSL before version 4.5.0 that mishandles TLS 1.3 server data in the WAIT_CERT_CR state.
How severe is CVE-2020-24613?
CVE-2020-24613 has a severity score of 6.8, which is considered medium.
How does CVE-2020-24613 affect Wolfssl?
CVE-2020-24613 affects Wolfssl versions up to but excluding version 4.5.0.
What is the impact of CVE-2020-24613?
CVE-2020-24613 allows attackers in a privileged network position to impersonate any TLS 1.3 server.
Is there a fix for CVE-2020-24613?
Yes, the fix for CVE-2020-24613 is to upgrade to version 4.5.0 or later of Wolfssl.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wolfssl
- canonical/wolfssl wolfssl