CVE-2021-28683

7.5 HIGH

📋 TL;DR

This vulnerability in Envoy proxy allows remote attackers to cause a denial of service by sending a specially crafted TLS alert with an unknown alert code, triggering a NULL pointer dereference and crash. It affects all Envoy deployments using TLS connections. The vulnerability is remotely exploitable without authentication.

💻 Affected Systems

Products:
  • Envoy Proxy
Versions: All versions through 1.71.1
Operating Systems: All platforms running Envoy
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects deployments using TLS connections. HTTP/1.1, HTTP/2, and HTTP/3 over TLS are all vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service outage of Envoy proxy, disrupting all traffic routing through the affected instance, potentially causing cascading failures in dependent services.

🟠

Likely Case

Denial of service affecting specific TLS connections, causing temporary service disruption until Envoy restarts automatically or manually.

🟢

If Mitigated

Minimal impact with proper monitoring and automatic restart mechanisms in place, though brief service interruptions may occur.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires sending a malformed TLS alert packet to a vulnerable Envoy instance. The vulnerability is simple to trigger and has been publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.72.0 and later

Vendor Advisory: https://github.com/envoyproxy/envoy/security/advisories/GHSA-r22g-5f3x-xjgg

Restart Required: Yes

Instructions:

1. Upgrade Envoy to version 1.72.0 or later. 2. Replace the Envoy binary with the patched version. 3. Restart the Envoy service. 4. Verify the new version is running.

🔧 Temporary Workarounds

TLS Alert Filtering

linux

Use network filtering to block TLS alert packets with unknown alert codes before they reach Envoy

iptables -A INPUT -p tcp --dport 443 -m string --hex-string '|15 03 03 00 02|' --algo bm -j DROP

🧯 If You Can't Patch

  • Implement network segmentation to limit which systems can send TLS traffic to Envoy instances
  • Deploy redundant Envoy instances with load balancing to maintain service during individual instance crashes

🔍 How to Verify

Check if Vulnerable:

Check Envoy version: envoy --version. If version is 1.71.1 or earlier, the system is vulnerable.

Check Version:

envoy --version | grep -o 'version: [0-9.]*'

Verify Fix Applied:

Verify Envoy version is 1.72.0 or later and monitor for crashes after applying the patch.

📡 Detection & Monitoring

Log Indicators:

  • Envoy process crashes
  • Segmentation fault errors in logs
  • Unexpected termination of Envoy service

Network Indicators:

  • TLS alert packets with unusual alert codes
  • Sudden drops in TLS connections

SIEM Query:

source="envoy.logs" AND ("segmentation fault" OR "crash" OR "terminated unexpectedly")

🔗 References

📤 Share & Export