CVE-2023-50469

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary code on affected Shenzhen Libituo LBT-T300-T310 routers by sending specially crafted requests to the /apply.cgi endpoint. Attackers can exploit a buffer overflow in the ApCliEncrypType parameter to gain full control of the device. Organizations using these specific router models with vulnerable firmware are affected.

💻 Affected Systems

Products:
  • Shenzhen Libituo Technology Co., Ltd LBT-T300
  • Shenzhen Libituo Technology Co., Ltd LBT-T310
Versions: v2.2.2.6
Operating Systems: Embedded Linux
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the web management interface accessible via HTTP. No special configuration is required to be vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device compromise leading to persistent backdoor installation, network traffic interception, lateral movement to connected systems, and potential data exfiltration.

🟠

Likely Case

Remote code execution allowing attackers to modify router configuration, intercept traffic, or use the device as a pivot point for further attacks.

🟢

If Mitigated

Limited impact if device is behind firewalls with strict ingress filtering and network segmentation prevents lateral movement.

🌐 Internet-Facing: HIGH - The vulnerability affects a web interface parameter and can be exploited remotely without authentication.
🏢 Internal Only: MEDIUM - Still significant risk from internal threats or compromised internal systems, but attack surface is reduced.

🎯 Exploit Status

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

Public proof-of-concept code is available in GitHub repositories. The vulnerability requires no authentication and has straightforward exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: Yes

Instructions:

1. Contact Shenzhen Libituo Technology for firmware updates. 2. If no patch is available, implement workarounds. 3. Consider replacing affected devices with supported alternatives.

🔧 Temporary Workarounds

Network Access Control

linux

Restrict access to the router's web management interface using firewall rules.

iptables -A INPUT -p tcp --dport 80 -s TRUSTED_IP -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j DROP

Disable Web Interface

all

If possible, disable the web management interface and use alternative management methods.

🧯 If You Can't Patch

  • Isolate affected routers in a dedicated network segment with strict firewall rules.
  • Implement network monitoring and intrusion detection specifically for traffic to/from these devices.

🔍 How to Verify

Check if Vulnerable:

Check router firmware version via web interface at http://router-ip/status.cgi or via SSH if available. Look for version v2.2.2.6.

Check Version:

curl -s http://router-ip/status.cgi | grep -i version

Verify Fix Applied:

Verify firmware version has been updated to a version later than v2.2.2.6. Test the /apply.cgi endpoint with controlled payloads in a lab environment.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /apply.cgi with long ApCliEncrypType parameters
  • Multiple failed authentication attempts followed by successful /apply.cgi access

Network Indicators:

  • HTTP requests to /apply.cgi with unusually long parameter values
  • Traffic patterns suggesting reverse shell connections from router IP

SIEM Query:

source="router_logs" AND uri_path="/apply.cgi" AND (param_length>100 OR status_code=500)

🔗 References

📤 Share & Export