# CVE-2020-24613: wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the WAIT_CERT_CR state, within SanityCheckTls13MsgReceived() in tls13.c.


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-24613, GHSA-m4j6-ffw6-5r4m, UBUNTU-CVE-2020-24613

## What is CVE-2020-24613?

CVE-2020-24613 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 24 Aug 2020. 

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2020-24613?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2020-24613?

Upgrade to a fixed version.

## Is CVE-2020-24613 being exploited?

There is no known exploitation of CVE-2020-24613 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24613 and fix it if it is affected.

What it is: CVE-2020-24613 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 24 Aug 2020. 
Exploitation: There is no known exploitation of CVE-2020-24613 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24613/ (Markdown: https://insights.sbomify.com/CVE-2020-24613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24613
- OSV: https://osv.dev/vulnerability/CVE-2020-24613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24613/
Summaries are generated and may contain mistakes; the official description above is the record.