Loading vulnerability…
A vulnerability in liblsquic/lsquic_qenc_hdl.c in LiteSpeed QUIC (LSQUIC) before version 3.1.0 arises from improper handling of the MAX_TABLE_CAPACITY parameter. This flaw could allow an attacker to exploit the way the library manages dynamic table capacity, potentially leading to memory corruption or other unexpected behavior.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides proof-of-concept (PoC) scripts for conducting denial-of-service (DoS) attacks against HTTP/3 (QUIC) servers, including a specific exploit for CVE-2022-30592 affecting the lsquic library (used by LiteSpeed servers). The repository contains three main attack scripts: 1. http3-flood/http3-flood.sh: A bash script that uses curl (with HTTP/3 support) to send a high volume of crafted HTTP/3 requests to a target URL, aiming to overwhelm the server (flood attack). The Dockerfile in the same directory is used to build a containerized environment with the necessary curl and quiche dependencies. 2. http3-loris/http3-loris.sh: A bash script that launches a slow-loris style attack using the aioquic Python library, sending many slow, incomplete HTTP/3 requests to exhaust server resources. 3. http3-stream(CVE-2022-30592)/http3-stream.sh: A bash script that automates the exploitation of CVE-2022-30592 by repeatedly launching Python aioquic client requests to a vulnerable server, potentially causing a denial of service. The scripts are intended for educational and research purposes, as referenced in the README.md, and require the user to specify the target URL. The attacks are network-based and target HTTP/3-enabled servers, with a focus on those using the vulnerable lsquic library. The repository is structured with clear separation of each attack type in its own directory, and includes setup instructions for both Python and Docker-based environments.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.