CVE-2024-27316·Apache vulnerability
HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.
- Severity
- high
- Software
- Apache
- Fixed in
- 2.4.59
- Published
- 2024-04-04
Affected versions
From: 2.4.17
Until: 2.4.59
Fixed in: 2.4.59
How to fix this CVE
Update Apache HTTP Server to version 2.4.59 or later to patch the HTTP/2 header buffering vulnerability. This fix prevents memory exhaustion attacks that exploit improper handling of oversized incoming headers. Prioritize this update for production systems exposed to untrusted network traffic, as the vulnerability requires no authentication or user interaction.
sudo dnf update httpdDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
Repeated or malformed HTTP/2 HEADERS frames with abnormally large header block sizes (exceeding LimitRequestFields or LimitRequestFieldSize thresholds) sent from a single client IP without completing the request lifecycle. Log pattern: 'h2.*headers.*exceeding' or abnormal increases in child process memory usage correlated with HTTP/2 connections.WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement HTTP/2 header size limits at the WAF level by rejecting HEADERS frames or requests with cumulative header size exceeding a reasonable threshold (e.g., 16KB total). Set rate limits on header-heavy requests per IP to mitigate header flooding attempts before they reach the Apache backend.How to check if you are affected
- Run 'apache2ctl -v' or 'httpd -v' to check the currently installed Apache version and compare it against 2.4.59.
- Verify HTTP/2 support is enabled by checking if mod_http2 is loaded: grep -i 'mod_http2' /etc/apache2/mods-enabled/* or httpd -M | grep http2.
- Search Apache access and error logs for repeated or sustained HTTP/2 HEADERS frame activity without corresponding request completion: grep -i 'h2' /var/log/apache2/error.log | tail -100.
- After patching, re-run 'apache2ctl -v' or 'httpd -v' to confirm the version is 2.4.59 or later, then restart Apache with 'sudo systemctl restart apache2' or 'sudo systemctl restart httpd' and verify normal operation.
FAQ
What is CVE-2024-27316?
CVE-2024-27316 is a denial-of-service vulnerability in Apache HTTP Server's HTTP/2 implementation where the server buffers excessively large incoming headers while attempting to generate a 413 response. An attacker can exploit this by continuously sending oversized headers, causing unbounded memory consumption and server crash.
Is CVE-2024-27316 being actively exploited?
No, according to CISA's Known Exploited Vulnerabilities (KEV) catalog, CVE-2024-27316 is not currently being exploited in the wild, and no public exploit code has been released.
What versions of Apache are affected by CVE-2024-27316?
Apache HTTP Server versions 2.4.17 through 2.4.58 are vulnerable. Version 2.4.59 and all subsequent releases include the fix.
How do I check if my server is vulnerable to CVE-2024-27316?
Execute 'apache2ctl -v' or 'httpd -v' and check if the version falls between 2.4.17 and 2.4.58. If HTTP/2 is enabled (verify with 'httpd -M | grep http2'), your server is vulnerable until you update to 2.4.59 or later.
Does Defensia detect CVE-2024-27316?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2024-27316 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-27316. Free for 1 server.
Get started free