CVE-2020-11100

8.8 HIGH

📋 TL;DR

This vulnerability allows remote attackers to write arbitrary bytes to heap memory via a crafted HTTP/2 request to HAProxy's HPACK decoder. Successful exploitation could lead to remote code execution, denial of service, or information disclosure. Affects HAProxy 1.8 through 2.x before version 2.1.4.

💻 Affected Systems

Products:
  • HAProxy
Versions: 1.8 through 2.x before 2.1.4
Operating Systems: Linux, BSD, Other Unix-like systems
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects configurations using HTTP/2. HTTP/1.x configurations are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution with the privileges of the HAProxy process, potentially leading to complete system compromise.

🟠

Likely Case

Denial of service through process crashes or memory corruption, disrupting load balancing services.

🟢

If Mitigated

Limited impact if proper network segmentation and least privilege principles are applied.

🌐 Internet-Facing: HIGH - HAProxy is typically deployed as an internet-facing reverse proxy/load balancer, making it directly accessible to attackers.
🏢 Internal Only: MEDIUM - Internal HAProxy instances could still be targeted by compromised internal systems or lateral movement.

🎯 Exploit Status

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

Exploit requires crafting specific HTTP/2 requests to trigger the heap corruption. Public proof-of-concept code exists.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.1.4 and later

Vendor Advisory: http://www.haproxy.org

Restart Required: Yes

Instructions:

1. Download HAProxy 2.1.4 or later from haproxy.org. 2. Compile and install the new version. 3. Replace the existing HAProxy binary. 4. Restart HAProxy service.

🔧 Temporary Workarounds

Disable HTTP/2

all

Disable HTTP/2 support in HAProxy configuration to prevent exploitation.

In HAProxy config, ensure no 'alpn h2' or similar HTTP/2 directives are present.

🧯 If You Can't Patch

  • Implement network segmentation to restrict access to HAProxy instances.
  • Deploy web application firewall (WAF) rules to detect and block malicious HTTP/2 traffic.

🔍 How to Verify

Check if Vulnerable:

Check HAProxy version with 'haproxy -v' and verify it's below 2.1.4 and at least 1.8.

Check Version:

haproxy -v

Verify Fix Applied:

After patching, run 'haproxy -v' and confirm version is 2.1.4 or higher.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected HAProxy process crashes
  • Memory corruption errors in system logs

Network Indicators:

  • Malformed HTTP/2 requests with unusual header patterns

SIEM Query:

source="haproxy.log" AND ("segmentation fault" OR "memory corruption" OR "invalid write")

🔗 References

📤 Share & Export