# CVE-2022-35409: Memory corruption in n/a

> An unauthenticated attacker can cause a server crash or information disclosure via a heap-based buffer over-read in Mbed TLS DTLS servers with specific configurations.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-35409, DEBIAN-CVE-2022-35409, GHSA-m52q-qpp4-f753, JLSEC-2025-218, MGASA-2022-0415, UBUNTU-CVE-2022-35409, openSUSE-SU-2024:12478-1

## What is CVE-2022-35409?

CVE-2022-35409 is a critical memory corruption vulnerability in Arm Mbed Tls, published on 15 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Mbed TLS before 2.28.1 and 3.x before 3.2.0. In some configurations, an unauthenticated attacker can send an invalid ClientHello message to a DTLS server that causes a heap-based buffer over-read of up to 255 bytes. This can cause a server crash or possibly information disclosure based on error responses. Affected configurations have MBEDTLS_SSL_DTLS_CLIENT_PORT_REUSE enabled and MBEDTLS_SSL_IN_CONTENT_LEN less than a threshold that depends on the configuration: 258 bytes if using mbedtls_ssl_cookie_check, and possibly up to 571 bytes with a custom cookie check function.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-35409?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mbedtls-2` | openSUSE:Tumbleweed | All versions | 2.28.1-1.1 |

Products: Arm Mbed Tls, Debian Debian Linux, Trustedfirmware Mbed Tls.

## How do I fix CVE-2022-35409?

Upgrade to a fixed version.

## Is CVE-2022-35409 being exploited?

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

## Other vulnerabilities in Arm Mbed Tls

- [CVE-2026-34877](https://insights.sbomify.com/CVE-2026-34877/): Deserialization in n/a (critical 9.8)
- [CVE-2022-46393](https://insights.sbomify.com/CVE-2022-46393/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-44732](https://insights.sbomify.com/CVE-2021-44732/): Use after free in n/a (critical 9.8)
- [CVE-2017-18187](https://insights.sbomify.com/CVE-2017-18187/): Integer overflow in n/a (critical 9.8)
- [CVE-2018-0487](https://insights.sbomify.com/CVE-2018-0487/): Memory corruption in ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35409 and fix it if it is affected.

What it is: CVE-2022-35409 is a critical memory corruption vulnerability in Arm Mbed Tls, published on 15 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35409 in the wild and no public exploit code.

Affected product: Arm Mbed Tls. 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-2022-35409/ (Markdown: https://insights.sbomify.com/CVE-2022-35409/index.md)
```

## Sources

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

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