# CVE-2023-51714: Integer overflow in n/a

> An integer overflow in Qt's HTTP2 HPack implementation can lead to denial of service, requiring users to upgrade the Qt library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 24 Dec 2023
- **Updated:** 8 Oct 2026
- **Also known as:** AZL-33517, AZL-38245, CLSA-2025-1762191563, DEBIAN-CVE-2023-51714, GHSA-4fvr-x23f-jwc4, OESA-2024-1161, SUSE-SU-2024:0063-1, SUSE-SU-2024:0138-1, UBUNTU-CVE-2023-51714, openSUSE-SU-2024:13553-1, openSUSE-SU-2024:13555-1

## What is CVE-2023-51714?

CVE-2023-51714 is a critical vulnerability in Debian Debian Linux, published on 24 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the HTTP2 implementation in Qt before 5.15.17, 6.x before 6.2.11, 6.3.x through 6.5.x before 6.5.4, and 6.6.x before 6.6.2. network/access/http2/hpacktable.cpp has an incorrect HPack integer overflow check.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-51714?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 5.15.8+kde185-150500.4.16.1 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 5.15.8+kde185-150500.4.16.1 |
| `qt6-base` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 6.4.2-150500.3.14.1 |
| `qt6-base` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 6.4.2-150500.3.14.1 |
| `libqt5-qtbase` | openSUSE:Leap 15.5 | All versions | 5.15.8+kde185-150500.4.16.1 |
| `qt6-base` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.14.1 |
| `qt6-base-docs` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.14.1 |
| `libqt5-qtbase` | openSUSE:Tumbleweed | All versions | 5.15.12+kde147-1.1 |
| `qt6-base` | openSUSE:Tumbleweed | All versions | 6.6.1-5.1 |

Products: Debian Debian Linux, Qt Qt.

## How do I fix CVE-2023-51714?

Upgrade to a fixed version.

## Is CVE-2023-51714 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51714 and fix it if it is affected.

What it is: CVE-2023-51714 is a critical vulnerability in Debian Debian Linux, published on 24 Dec 2023. 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-2023-51714 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2023-51714/ (Markdown: https://insights.sbomify.com/CVE-2023-51714/index.md)
```

## Sources

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

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