# CVE-2024-30161: Use after free in n/a

> A dangling pointer in Qt WebAssembly allows attackers to access freed memory, potentially leading to code execution or crashes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2024
- **Updated:** 14 Mar 2025
- **Also known as:** AZL-38545, GHSA-5gxc-5wfv-r5f9, SUSE-SU-2024:1174-1, UBUNTU-CVE-2024-30161, openSUSE-SU-2024:13844-1

## What is CVE-2024-30161?

CVE-2024-30161 is a medium-severity use after free vulnerability in Qt Qt, published on 24 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Qt 6.5.4, 6.5.5, and 6.6.2, QNetworkReply header data might be accessed via a dangling pointer in Qt for WebAssembly (wasm). (Earlier and later versions are unaffected.)

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qt6-base` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 6.4.2-150500.3.17.1 |
| `qt6-base` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 6.4.2-150500.3.17.1 |
| `qt6-base` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.17.1 |
| `qt6-base-docs` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.17.1 |
| `qt6-base` | openSUSE:Tumbleweed | All versions | 6.7.0-1.1 |

Products: Qt Qt.

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

Upgrade to a fixed version.

## Is CVE-2024-30161 being exploited?

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

## Other vulnerabilities in Qt Qt

- [CVE-2020-12267](https://insights.sbomify.com/CVE-2020-12267/): Use after free in n/a (critical 9.8)
- [CVE-2017-10904](https://insights.sbomify.com/CVE-2017-10904/): Command injection in Qt for Android (critical 9.8)
- [CVE-2011-3194](https://insights.sbomify.com/CVE-2011-3194/): Memory corruption in n/a (critical 9.3)
- [CVE-2022-40983](https://insights.sbomify.com/CVE-2022-40983/): Integer overflow in Qt (high 8.8)
- [CVE-2022-43591](https://insights.sbomify.com/CVE-2022-43591/): Memory corruption in Qt (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30161 and fix it if it is affected.

What it is: CVE-2024-30161 is a medium-severity use after free vulnerability in Qt Qt, published on 24 Mar 2024. 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-2024-30161 in the wild and no public exploit code.

Affected product: Qt Qt. 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-30161/ (Markdown: https://insights.sbomify.com/CVE-2024-30161/index.md)
```

## Sources

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

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