CVE-2021-35327

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to enable Telnet service on TOTOLINK A720R routers via a crafted POST request, then gain access using default credentials. Attackers can achieve remote code execution and full device compromise. Only TOTOLINK A720R routers running vulnerable firmware versions are affected.

💻 Affected Systems

Products:
  • TOTOLINK A720R
Versions: A720R_Firmware v4.1.5cu.470_B20200911 and likely earlier versions
Operating Systems: Embedded Linux (router firmware)
Default Config Vulnerable: ⚠️ Yes
Notes: Default configuration is vulnerable. Telnet service is disabled by default but can be enabled via the exploit.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete router takeover allowing traffic interception, credential theft, network pivoting, and persistent backdoor installation.

🟠

Likely Case

Router compromise leading to DNS hijacking, credential harvesting, and botnet recruitment.

🟢

If Mitigated

Limited impact if Telnet is disabled, strong credentials are set, and network segmentation isolates the router.

🌐 Internet-Facing: HIGH - Routers are typically internet-facing, allowing remote exploitation without authentication.
🏢 Internal Only: MEDIUM - Internal attackers could exploit if they reach the management interface.

🎯 Exploit Status

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

Exploit requires sending a single crafted POST request. Default credentials (admin:admin) are well-known.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check TOTOLINK for updated firmware

Vendor Advisory: No official vendor advisory found

Restart Required: Yes

Instructions:

1. Visit TOTOLINK support website. 2. Download latest firmware for A720R. 3. Access router admin panel. 4. Upload and apply firmware update. 5. Reboot router.

🔧 Temporary Workarounds

Disable Telnet service

all

Manually disable Telnet service in router configuration

Change default credentials

all

Change admin password from default to strong unique password

🧯 If You Can't Patch

  • Isolate router on separate VLAN with strict firewall rules
  • Disable remote management and restrict admin interface to internal network only

🔍 How to Verify

Check if Vulnerable:

Check if router responds to crafted POST request enabling Telnet, then test Telnet login with default credentials

Check Version:

Login to router admin panel and check firmware version in system status

Verify Fix Applied:

Attempt exploitation after patch - should fail. Verify Telnet service cannot be enabled via POST request.

📡 Detection & Monitoring

Log Indicators:

  • POST requests to unusual endpoints
  • Telnet service startup logs
  • Failed/successful Telnet authentication attempts

Network Indicators:

  • Unexpected Telnet port (23) traffic
  • POST requests to router management interface from external sources

SIEM Query:

source_ip=external AND dest_ip=router_ip AND (http_method=POST AND uri_contains="cgi-bin" OR port=23)

🔗 References

📤 Share & Export