ubuntu-cve-2024-52811
Vulnerability from osv_ubuntu
Published
2024-11-25 19:15
Modified
2026-05-26 07:18
Summary
Details

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.

Severity
8.2 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
N/A (UNKNOWN)
medium
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libngtcp2-0",
            "binary_version": "0.1.0+dfsg-1ubuntu0.1~esm1"
          },
          {
            "binary_name": "libngtcp2-crypto-gnutls0",
            "binary_version": "0.1.0+dfsg-1ubuntu0.1~esm1"
          },
          {
            "binary_name": "ngtcp2-client",
            "binary_version": "0.1.0+dfsg-1ubuntu0.1~esm1"
          },
          {
            "binary_name": "ngtcp2-server",
            "binary_version": "0.1.0+dfsg-1ubuntu0.1~esm1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:22.04:LTS",
        "name": "ngtcp2",
        "purl": "pkg:deb/ubuntu/ngtcp2@0.1.0+dfsg-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0~20210905-1",
        "0.1.0+dfsg-1",
        "0.1.0+dfsg-1ubuntu0.1~esm1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libngtcp2-9",
            "binary_version": "0.12.1+dfsg-1+deb12u1build0.24.04.1"
          },
          {
            "binary_name": "libngtcp2-crypto-gnutls2",
            "binary_version": "0.12.1+dfsg-1+deb12u1build0.24.04.1"
          },
          {
            "binary_name": "ngtcp2-client",
            "binary_version": "0.12.1+dfsg-1+deb12u1build0.24.04.1"
          },
          {
            "binary_name": "ngtcp2-server",
            "binary_version": "0.12.1+dfsg-1+deb12u1build0.24.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "ngtcp2",
        "purl": "pkg:deb/ubuntu/ngtcp2@0.12.1+dfsg-1+deb12u1build0.24.04.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.12.1+dfsg-1",
        "0.12.1+dfsg-1build1",
        "0.12.1+dfsg-1build2",
        "0.12.1+dfsg-1+deb12u1build0.24.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libngtcp2-16",
            "binary_version": "1.11.0-1+deb13u1build0.25.10.1"
          },
          {
            "binary_name": "libngtcp2-crypto-gnutls8",
            "binary_version": "1.11.0-1+deb13u1build0.25.10.1"
          },
          {
            "binary_name": "ngtcp2-client",
            "binary_version": "1.11.0-1+deb13u1build0.25.10.1"
          },
          {
            "binary_name": "ngtcp2-server",
            "binary_version": "1.11.0-1+deb13u1build0.25.10.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:25.10",
        "name": "ngtcp2",
        "purl": "pkg:deb/ubuntu/ngtcp2@1.11.0-1+deb13u1build0.25.10.1?arch=source\u0026distro=questing"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.11.0-1",
        "1.11.0-1+deb13u1build0.25.10.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libngtcp2-16",
            "binary_version": "1.16.0-1ubuntu0.1"
          },
          {
            "binary_name": "libngtcp2-crypto-gnutls8",
            "binary_version": "1.16.0-1ubuntu0.1"
          },
          {
            "binary_name": "libngtcp2-crypto-ossl0",
            "binary_version": "1.16.0-1ubuntu0.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.04:LTS",
        "name": "ngtcp2",
        "purl": "pkg:deb/ubuntu/ngtcp2@1.16.0-1ubuntu0.1?arch=source\u0026distro=resolute"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.11.0-1",
        "1.16.0-1",
        "1.16.0-1ubuntu0.1"
      ]
    }
  ],
  "aliases": [],
  "details": "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.",
  "id": "UBUNTU-CVE-2024-52811",
  "modified": "2026-05-26T07:18:31Z",
  "published": "2024-11-25T19:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2024-52811"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-52811"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/ngtcp2/ngtcp2/security/advisories/GHSA-4gmv-gf46-r4g5"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/ngtcp2/ngtcp2/commit/44b662bd139c23fee1703bf256c13349e2e624a1"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/ngtcp2/ngtcp2/commit/e550c1a414318d0f3f01fca1a621ae0b0428ca15"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2024-52811"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.