CVE-2024-52811
HIGHDescription
The ngtcp2 project is an effort to implement IETF QUIC protocol in C. In affected versions acks are not validated before being written to the qlog leading to a buffer overflow. In `ngtcp2_conn::conn_recv_pkt` for an ACK, there was new logic that got added to skip `conn_recv_ack` if an ack has already been processed in the payload. However, this causes us to also skip `ngtcp2_pkt_validate_ack`. The ack which was skipped still got written to qlog. The bug occurs in `ngtcp2_qlog::write_ack_frame`. It is now possible to reach this code with an invalid ack, suppose `largest_ack=0` and `first_ack_range=15`. Subtracting `largest_ack - first_ack_range` will lead to an integer underflow which is 20 chars long. However, the ngtcp2 qlog code assumes the number written is a signed integer and only accounts for 19 characters of overhead (see `NGTCP2_QLOG_ACK_FRAME_RANGE_OVERHEAD`). Therefore, we overwrite the buffer causing a heap overflow. This is high priority and could potentially impact many users if they enable qlog. qlog is disabled by default. Due to its overhead, it is most likely used for debugging purpose, but the actual use is unknown. ngtcp2 v1.9.1 fixes the bug and users are advised to upgrade. Users unable to upgrade should not turn on qlog.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 53% of all known CVEs.
References
Related Vulnerabilities
Other CWE-670 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-9425 | High | 7.5 | 17% | - | Fix |
| CVE-2019-9946 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-32896 | High | 7.8 | 3.0% | KEV | - |
| CVE-2019-17192 | Critical | 9.8 | 2.7% | - | - |
| CVE-2026-38361 | High | 7.5 | 2.6% | - | - |
| CVE-2020-1914 | Critical | 9.8 | 2.5% | - | Fix |
Common questions
How do I fix CVE-2024-52811?
No published fix for CVE-2024-52811 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2024-52811 being actively exploited?
Not that we know of. CVE-2024-52811 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.80% is the estimated probability that it will be exploited in the next 30 days. That is higher than 53% of all scored CVEs.
How severe is CVE-2024-52811?
CVE-2024-52811 has a CVSS v3 base score of 8.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2024-52811
Markdown
[](https://tridentstack.com/cve/CVE-2024-52811)HTML
<a href="https://tridentstack.com/cve/CVE-2024-52811"><img src="https://tridentstack.com/cve/badge/CVE-2024-52811.svg" alt="CVE-2024-52811"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-25.