Loading vulnerability…
CVE-2023-43622 is a denial-of-service vulnerability in Apache HTTP Server affecting versions 2.4.55 through 2.4.57. A remote attacker can open an HTTP/2 connection and set the initial flow-control window size to 0, causing the server to block handling of that connection indefinitely. This behavior can tie up worker resources in a manner analogous to a Slowloris-style resource exhaustion attack. The issue was corrected in Apache HTTP Server 2.4.58 by ensuring such stalled connections are terminated after the configured connection timeout.
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 contains a single Python script, 'exploit.py', which implements a denial-of-service (DoS) attack against an HTTP/2-capable server. The script uses the 'h2' library to establish an HTTP/2 connection to a specified target IP address (hardcoded as 200.146.193.143) on port 443 (HTTPS). It manipulates the HTTP/2 window size setting to 0 and floods the server with repeated GET requests using multiple threads (10 by default). The purpose is to exhaust server resources and potentially cause a DoS condition. The script is operational and can be used as-is, provided the attacker has network access to the target and the required Python dependencies are installed. No specific CVE or product is referenced, and the attack is generic to HTTP/2 servers.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.