Loading vulnerability…
A vulnerability in quic-go through 0.27.0 allows remote attackers to cause a denial of service by sending incomplete QUIC or HTTP/3 requests, exploiting a flaw in mtu_discoverer.go where the MTU Discovery service is misparsed, leading to an overflow of the probe timer and excessive CPU consumption.
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 scripts for exploiting vulnerabilities in QUIC-enabled servers, with a focus on CVE-2022-30591 (QUIC-Loris) affecting the quic-go library and Caddy server. The structure includes three main attack scripts: (1) 'quic-loris-CVE-2022-30591.sh' for the QUIC-Loris slow DoS attack, (2) 'quic-flooding.sh' for mass connection flooding, and (3) 'quic-hash.py' for sending crafted UDP packets to stress server processing. The scripts are written in Bash and Python, require the user to specify the target server's URL or IP, and depend on Python libraries such as aioquic and Scapy. The attacks are network-based and target the QUIC protocol, aiming to exhaust server resources and cause denial of service. The repository is intended for educational and research purposes, as referenced in the README and associated academic publication.
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.