CVE-2020-11996

7.5 HIGH

📋 TL;DR

This CVE describes a denial-of-service vulnerability in Apache Tomcat's HTTP/2 implementation where specially crafted requests can cause high CPU usage, potentially making the server unresponsive. It affects Tomcat versions 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35, and 8.5.0 to 8.5.55. Organizations running these Tomcat versions with HTTP/2 enabled are vulnerable.

💻 Affected Systems

Products:
  • Apache Tomcat
Versions: 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35, 8.5.0 to 8.5.55
Operating Systems: All operating systems running affected Tomcat versions
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when HTTP/2 protocol is enabled. HTTP/1.1 connections are not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service unavailability due to resource exhaustion, leading to extended downtime for web applications hosted on affected Tomcat instances.

🟠

Likely Case

Temporary performance degradation or intermittent service interruptions during attack periods, affecting application availability.

🟢

If Mitigated

Minimal impact with proper monitoring and rate limiting in place, allowing quick detection and mitigation of attack attempts.

🌐 Internet-Facing: HIGH - Internet-facing Tomcat servers are directly exposed to potential DoS attacks from untrusted sources.
🏢 Internal Only: MEDIUM - Internal servers could still be targeted by compromised internal systems or malicious insiders.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending specially crafted HTTP/2 requests, which can be automated. No authentication is required to trigger the vulnerability.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Tomcat 10.0.0-M6, 9.0.36, 8.5.56

Vendor Advisory: https://lists.apache.org/thread.html/r2529016c311ce9485e6f173446d469600fdfbb94dccadfcd9dfdac79%40%3Cusers.tomcat.apache.org%3E

Restart Required: Yes

Instructions:

1. Download the patched version from Apache Tomcat website. 2. Stop the Tomcat service. 3. Backup current installation. 4. Replace with patched version. 5. Restart Tomcat service.

🔧 Temporary Workarounds

Disable HTTP/2

all

Disable HTTP/2 protocol support in Tomcat configuration to prevent exploitation

Edit server.xml and remove or comment out HTTP/2 connector configurations

Implement Rate Limiting

linux

Configure web application firewall or load balancer to limit concurrent HTTP/2 connections

# Example using iptables for connection limiting
iptables -A INPUT -p tcp --dport 8443 -m connlimit --connlimit-above 100 -j REJECT

🧯 If You Can't Patch

  • Implement network-level controls to limit HTTP/2 traffic to trusted sources only
  • Deploy monitoring with alerting for abnormal CPU spikes on Tomcat servers

🔍 How to Verify

Check if Vulnerable:

Check Tomcat version and verify HTTP/2 is enabled in server.xml configuration

Check Version:

grep 'Server version' $CATALINA_HOME/logs/catalina.out | tail -1

Verify Fix Applied:

Verify Tomcat version is 10.0.0-M6+, 9.0.36+, or 8.5.56+ and test HTTP/2 functionality

📡 Detection & Monitoring

Log Indicators:

  • Unusual patterns of HTTP/2 connection attempts
  • High CPU usage alerts from monitoring systems
  • Tomcat thread pool exhaustion warnings

Network Indicators:

  • Spikes in HTTP/2 traffic from single or multiple sources
  • Unusual HTTP/2 request patterns

SIEM Query:

source="tomcat.logs" AND ("HTTP/2" OR "h2") AND ("high cpu" OR "connection limit" OR "thread pool")

🔗 References

📤 Share & Export