CVE-2022-25130

9.8 CRITICAL

📋 TL;DR

This CVE describes a command injection vulnerability in TOTOLINK router firmware that allows attackers to execute arbitrary commands via crafted MQTT packets. Attackers can gain full control of affected routers, potentially compromising network security. Users of TOTOLINK T6 and T10 routers with specific vulnerable firmware versions are affected.

💻 Affected Systems

Products:
  • TOTOLINK T6 router
  • TOTOLINK T10 router
Versions: T6 V3_Firmware T6_V3_V4.1.5cu.748_B20211015 and T10 V2_Firmware V4.1.8cu.5207_B20210320
Operating Systems: Embedded Linux firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default configurations. MQTT service may be enabled by default on affected firmware.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete router compromise leading to network takeover, credential theft, lateral movement to internal systems, and persistent backdoor installation.

🟠

Likely Case

Router compromise allowing traffic interception, DNS manipulation, credential harvesting, and use as attack platform.

🟢

If Mitigated

Limited impact if routers are behind firewalls with strict MQTT traffic filtering and network segmentation.

🌐 Internet-Facing: HIGH - Routers are typically internet-facing devices, and MQTT services may be exposed to WAN.
🏢 Internal Only: MEDIUM - Internal attackers could exploit if they have network access to router management interfaces.

🎯 Exploit Status

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

Public proof-of-concept exists in GitHub repository. Exploitation requires sending crafted MQTT packets to vulnerable routers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not found in provided references

Restart Required: Yes

Instructions:

1. Check TOTOLINK website for firmware updates
2. Download latest firmware for your model
3. Access router admin interface
4. Navigate to firmware upgrade section
5. Upload and apply new firmware
6. Reboot router after update

🔧 Temporary Workarounds

Disable MQTT service

all

Disable MQTT functionality if not required for operations

Access router admin interface -> Advanced Settings -> MQTT Configuration -> Disable

Network isolation

linux

Block MQTT traffic (port 1883 typically) at network perimeter

iptables -A INPUT -p tcp --dport 1883 -j DROP
iptables -A INPUT -p udp --dport 1883 -j DROP

🧯 If You Can't Patch

  • Isolate affected routers in separate VLAN with strict firewall rules
  • Implement network monitoring for MQTT traffic anomalies and command injection attempts

🔍 How to Verify

Check if Vulnerable:

Check router firmware version in admin interface. If matches affected versions and MQTT is enabled, device is vulnerable.

Check Version:

Login to router admin interface and check System Status or Firmware Information page

Verify Fix Applied:

Verify firmware version is updated beyond vulnerable versions. Test MQTT service with safe payloads to confirm command injection is patched.

📡 Detection & Monitoring

Log Indicators:

  • Unusual MQTT connection attempts
  • Suspicious command execution in router logs
  • Failed firmware update attempts

Network Indicators:

  • MQTT traffic to router on port 1883 with unusual payloads
  • Outbound connections from router to unknown destinations

SIEM Query:

source="router_logs" AND ("MQTT" OR "updateWifiInfo") AND ("exec" OR "system" OR "command")

🔗 References

📤 Share & Export