A vulnerability in Lighttpd versions 1.4.56 through 1.4.58 allows remote attackers to cause a denial of service by sending requests with large headers. Due to a typo in the connection_read_header_more function in connections.c, the server mishandles multiple read operations on large headers, resulting in stuck connections 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 a working exploit for CVE-2022-30780, a denial-of-service vulnerability in the lighttpd web server (versions 1.4.56, 1.4.57, 1.4.58). The main exploit script, 'CVE-2022-30780-lighttpd-denial-of-service.py', is a Python 3 tool that performs a DoS attack by sending a large number of HTTP requests with excessively long URLs to the target server, causing it to become unresponsive. The script includes logic to determine the maximum URL length the server can handle and then launches a multi-threaded attack to exhaust server resources. The repository also contains a comprehensive test environment under the 'tests/' directory, with Dockerfiles and Makefiles for various lighttpd versions, allowing users to set up vulnerable instances for testing. Additional scripts, such as 'generate_tests.py', automate the setup and testing process. The exploit is unauthenticated and targets network-accessible lighttpd servers. No fake or destructive code is present beyond the intended DoS functionality.
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.