CVE-2020-11984

9.8 CRITICAL

📋 TL;DR

CVE-2020-11984 is a critical vulnerability in Apache HTTP Server's mod_proxy_uwsgi module that allows attackers to disclose sensitive information and potentially execute arbitrary code. It affects Apache versions 2.4.32 through 2.4.44 when mod_proxy_uwsgi is enabled. Attackers can exploit this by sending specially crafted requests to vulnerable servers.

💻 Affected Systems

Products:
  • Apache HTTP Server
Versions: 2.4.32 to 2.4.44
Operating Systems: All operating systems running affected Apache versions
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when mod_proxy_uwsgi module is enabled and configured. Default Apache installations typically do not have this module enabled.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data theft, and lateral movement within the network.

🟠

Likely Case

Information disclosure of sensitive server data and memory contents, potentially leading to credential theft or further exploitation.

🟢

If Mitigated

Limited impact with proper network segmentation, WAF protection, and minimal exposed services.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit code is available. Exploitation requires sending specially crafted HTTP requests to vulnerable endpoints.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apache HTTP Server 2.4.46 and later

Vendor Advisory: https://httpd.apache.org/security/vulnerabilities_24.html

Restart Required: Yes

Instructions:

1. Upgrade Apache HTTP Server to version 2.4.46 or later. 2. Restart the Apache service. 3. Verify the patch is applied by checking the version.

🔧 Temporary Workarounds

Disable mod_proxy_uwsgi

linux

Disable the vulnerable module if not required for functionality

a2dismod proxy_uwsgi
systemctl restart apache2

Restrict access to proxy endpoints

linux

Use firewall rules to restrict access to uWSGI proxy endpoints

iptables -A INPUT -p tcp --dport 80 -m string --string "uwsgi" --algo bm -j DROP

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block malicious uWSGI requests
  • Isolate affected servers in a segmented network with strict access controls

🔍 How to Verify

Check if Vulnerable:

Check Apache version and mod_proxy_uwsgi status: httpd -v && httpd -M | grep proxy_uwsgi

Check Version:

httpd -v

Verify Fix Applied:

Verify Apache version is 2.4.46 or later: httpd -v

📡 Detection & Monitoring

Log Indicators:

  • Unusual HTTP requests containing uWSGI protocol manipulation
  • Multiple failed requests to proxy endpoints
  • Memory access errors in Apache logs

Network Indicators:

  • HTTP requests with malformed uWSGI headers
  • Traffic patterns indicating attempted exploitation

SIEM Query:

source="apache_access.log" AND (uri="*uwsgi*" OR user_agent="*exploit*" OR status=500)

🔗 References

📤 Share & Export