In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to header_out_dynamic_entry and es_max_header_list_size.
Product
litespeedtech lsquic vulnerabilities
5 published CVES affecting litespeedtech lsquic, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 2
- High
- 2
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest litespeedtech lsquic CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.45%
-
HighCVSS 7.5 EPSS 0.84%
LiteSpeed QUIC (LSQUIC) Library before 4.3.1 has an lsquic_engine_packet_in memory leak.
-
MediumCVSS 5.3 EPSS 0.68%
A hash collision vulnerability (in the hash table used to manage connections) in LSQUIC (aka LiteSpeed QUIC) before 4.2.0 allows remote attackers to cause a considerable CPU load on the server (a Hash DoS attack) by initiating connections with colliding Source Connection IDs (SCI...
-
CVE-2024-25678 In LiteSpeed QUIC (LSQUIC) Library before 4.0.4, DCID validation is mishandled.
PublishedCriticalCVSS 9.8 EPSS 0.35%In LiteSpeed QUIC (LSQUIC) Library before 4.0.4, DCID validation is mishandled.
-
CriticalCVSS 9.8 EPSS 3.3%
liblsquic/lsquic_qenc_hdl.c in LiteSpeed QUIC (aka LSQUIC) before 3.1.0 mishandles MAX_TABLE_CAPACITY.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.