# CVE-2024-23170: Information disclosure in n/a

> A local attacker can recover plaintext via a timing side channel in RSA operations by sending many decryption requests.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2024-23170, AZL-47697, DEBIAN-CVE-2024-23170, GHSA-w2fw-qqqw-v63m, JLSEC-2025-223, ROOT-OS-DEBIAN-12-CVE-2024-23170, UBUNTU-CVE-2024-23170, openSUSE-SU-2024:0037-1, openSUSE-SU-2024:13639-1, openSUSE-SU-2024:13640-1

## What is CVE-2024-23170?

CVE-2024-23170 is a medium-severity vulnerability in Arm Mbed Tls, published on 31 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2. There was a timing side channel in RSA private operations. This side channel could be sufficient for a local attacker to recover the plaintext. It requires the attacker to send a large number of messages for decryption, as described in "Everlasting ROBOT: the Marvin Attack" by Hubert Kario.

Weakness: CWE-203 (Observable Discrepancy), CWE-385 (Covert Timing Channel)

## Which versions are affected by CVE-2024-23170?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mbedtls` | SUSE:Package Hub 15 SP5 | All versions | 2.28.7-bp155.2.3.1 |
| `mbedtls` | openSUSE:Leap 15.5 | All versions | 2.28.7-bp155.2.3.1 |
| `mbedtls` | openSUSE:Tumbleweed | All versions | 3.5.2-1.1 |
| `mbedtls-2` | openSUSE:Tumbleweed | All versions | 2.28.7-1.1 |

Products: Arm Mbed Tls, Trustedfirmware Mbed Tls.

## How do I fix CVE-2024-23170?

Upgrade to a fixed version.

## Is CVE-2024-23170 being exploited?

There is no known exploitation of CVE-2024-23170 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-2024-23170 and fix it if it is affected.

What it is: CVE-2024-23170 is a medium-severity vulnerability in Arm Mbed Tls, published on 31 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23170 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-2024-23170/ (Markdown: https://insights.sbomify.com/CVE-2024-23170/index.md)
```

## Sources

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

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