CVE-2023-24142

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary commands on TOTOLINK CA300-PoE routers by injecting malicious commands into the NetDiagPingSize parameter. Attackers can gain full control of affected devices, potentially compromising network security. All users of vulnerable TOTOLINK CA300-PoE routers are affected.

💻 Affected Systems

Products:
  • TOTOLINK CA300-PoE
Versions: V6.2c.884
Operating Systems: Embedded Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the web management interface of the router. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device takeover leading to network compromise, data exfiltration, lateral movement to other devices, and persistent backdoor installation.

🟠

Likely Case

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

🟢

If Mitigated

Limited impact if device is behind firewall with strict inbound filtering and command injection attempts are blocked.

🌐 Internet-Facing: HIGH - Routers are typically internet-facing, making them directly accessible to attackers.
🏢 Internal Only: MEDIUM - Internal attackers could exploit if they have network access to the device.

🎯 Exploit Status

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

Public proof-of-concept available on GitHub. Exploitation requires sending crafted HTTP request to vulnerable endpoint.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Check TOTOLINK website for firmware updates. If update available: 1. Download latest firmware from vendor site 2. Log into router admin interface 3. Navigate to firmware update section 4. Upload and apply new firmware 5. Reboot router

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict access to router 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 Remote Management

all

Disable web management interface from WAN/remote access

🧯 If You Can't Patch

  • Isolate affected routers in separate VLAN with strict access controls
  • Implement network monitoring for unusual outbound connections from routers

🔍 How to Verify

Check if Vulnerable:

Check router firmware version via web interface at System Status > Firmware Version

Check Version:

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

Verify Fix Applied:

Verify firmware version is newer than V6.2c.884 and test with known exploit payloads

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /cgi-bin/cstecgi.cgi with shell metacharacters in parameters
  • Commands like 'ping' with unusual size parameters containing semicolons or pipes

Network Indicators:

  • HTTP requests containing shell commands in NetDiagPingSize parameter
  • Outbound connections from router to unexpected destinations

SIEM Query:

source="router_logs" AND uri="/cgi-bin/cstecgi.cgi" AND (NetDiagPingSize="*;*" OR NetDiagPingSize="*|*" OR NetDiagPingSize="*`*")

🔗 References

📤 Share & Export