Loading vulnerability…
CVE-2024-27316 is an uncontrolled resource-consumption vulnerability in Apache HTTP Server HTTP/2 processing involving nghttp2. When incoming HTTP/2 headers exceed the configured limit, nghttp2 temporarily buffers the headers to generate an HTTP 413 response. A client that continues transmitting headers can cause continued memory consumption and exhaust available memory.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2024-27316, an HTTP/2 CONTINUATION flood vulnerability affecting Apache httpd 2.4.58. The repository includes Docker configurations to set up both a vulnerable (2.4.58) and a fixed (2.4.59) Apache httpd server, exposing them on localhost ports 3392/3393 (vulnerable) and 3394/3395 (fixed). The main exploit logic resides in 'poc.js', a Node.js script that establishes an HTTP/2 connection to the target server and sends a HEADERS frame followed by a large number of CONTINUATION frames, aiming to exhaust server resources and demonstrate a denial-of-service condition. The exploit is intended for local testing against the provided Dockerized environment. Supporting files include Dockerfiles for each server version, a docker-compose.yml for orchestration, and package files for Node.js dependencies. The repository is structured for easy setup and demonstration of the vulnerability, with clear separation between vulnerable and fixed server instances.
This repository contains a Go-based proof-of-concept (PoC) exploit for CVE-2024-27316, a vulnerability affecting HTTP/2 servers. The main exploit logic resides in 'main.go', which implements a Denial of Service (DoS) attack by opening multiple concurrent connections (threads) to a specified HTTP/2 server and sending a continuous stream of oversized, random HTTP/2 header frames. The exploit can target both unencrypted (http) and TLS-encrypted (https) HTTP/2 servers, as specified by the user via command-line arguments. The README provides usage instructions and references the CERT advisory. No hardcoded IPs or domains are present; the user supplies the target at runtime. The repository is structured with standard Go project files and a single main exploit file. The exploit is a PoC and does not include advanced payloads or automation for weaponization.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously addressed Apache HTTP/2 CONTINUATION flood vulnerability, mentioned as historical context for mod_http2 hardening.
An important-severity vulnerability referenced by an AlmaLinux 9.2 local security-check plugin. The supplied CVSS v3 vector indicates an unauthenticated network-accessible flaw with low attack complexity and high availability impact.
A network-accessible, low-complexity vulnerability requiring no privileges or user interaction that can cause high availability impact. The supplied content does not identify the affected component or describe the technical flaw.
A memory exhaustion denial-of-service vulnerability in Apache HTTP Server's handling of oversized HTTP/2 headers buffered via nghttp2.
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.