Vulnerability record · CVE-2020-11993 · published 7 August 2020
CVE-2020-11993: Apache HTTP Server mod_http2 memory pool misuse under debug logging
Apache · Http Server
Apache HTTP Server 2.4.20 through 2.4.43, when trace/debug logging is enabled for the HTTP/2 module, can write log statements to the wrong connection under certain traffic edge patterns, causing concurrent use of memory pools. This is classified as CWE-444 (HTTP request smuggling) and can crash or destabilize the server. It only applies when mod_http2 LogLevel is set above "info".
Description
Apache HTTP Server versions 2.4.20 to 2.4.43 When trace/debug was enabled for the HTTP/2 module and on certain traffic edge patterns, logging statements were made on the wrong connection, causing concurrent use of memory pools. Configuring the LogLevel of mod_http2 above "info" will mitigate this vulnerability for unpatched servers.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Automated analysis
high priorityHigh CVSS (7.5) and very high EPSS with public exploit material, but exploitation requires non-default debug logging, limiting real-world exposure.
What it is
Apache HTTP Server 2.4.20 through 2.4.43, when trace/debug logging is enabled for the HTTP/2 module, can write log statements to the wrong connection under certain traffic edge patterns, causing concurrent use of memory pools. This is classified as CWE-444 (HTTP request smuggling) and can crash or destabilize the server. It only applies when mod_http2 LogLevel is set above "info".
Impact
An unauthenticated remote attacker can trigger concurrent memory pool use, causing denial of service through server crashes or instability. No confidentiality or integrity impact is described.
Attack surface
Reached over the network via HTTP/2 traffic to an affected server; no authentication or user interaction is required per the CVSS vector (AV:N/AC:L/PR:N/UI:N). Exploitation depends on trace/debug logging being enabled for mod_http2 and specific traffic edge patterns.
Exploitation
Not listed in CISA KEV and no ransomware group usage is documented, but EPSS is high (0.56448, 99th percentile) and a Packet Storm exploit reference exists, indicating public exploit material is available.
What to do
- Upgrade Apache HTTP Server past 2.4.43 to a fixed release
- If patching is delayed, set mod_http2 LogLevel to "info" or lower to remove the vulnerable condition
- Audit configurations for trace/debug logging on mod_http2 and revert to default levels
- Apply vendor patches for bundled Apache HTTP Server in NetApp, Oracle, Canonical, Debian, Fedora and openSUSE products
- Monitor for vendor advisories covering the affected product list
Detection
- Search httpd configurations for LogLevel values above "info" on mod_http2
- Monitor Apache error and crash logs for abnormal terminations or memory pool errors on HTTP/2 connections
- Alert on unexpected HTTP/2 traffic patterns that coincide with debug logging being enabled
- Track server restarts or availability drops on hosts running affected Apache versions
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
13 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2020-11993 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2020-11993), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.