CVE-2019-3412

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary commands on ZTE MF920 mobile hotspot devices. Attackers can exploit insufficient parameter validation in certain interfaces to run system commands with elevated privileges. All versions up to BD_R218V2.4 are affected.

💻 Affected Systems

Products:
  • ZTE MF920 Mobile Hotspot
Versions: All versions up to BD_R218V2.4
Operating Systems: Embedded Linux-based firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Affects web management interface and potentially other administrative interfaces. Device typically exposed to network when in use.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device compromise allowing attacker to install persistent backdoors, intercept all network traffic, modify device firmware, and use device as pivot point into internal networks.

🟠

Likely Case

Attacker gains administrative control of device, can monitor/modify traffic, change device settings, and potentially access connected devices.

🟢

If Mitigated

If network segmentation and access controls are properly implemented, impact limited to isolated device compromise without lateral movement.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Vulnerability is in web interface with no authentication required. Exploitation requires network access to device management interface.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: BD_R218V2.5 and later

Vendor Advisory: http://support.zte.com.cn/support/news/LoopholeInfoDetail.aspx?newsId=1010686

Restart Required: Yes

Instructions:

1. Download latest firmware from ZTE support site. 2. Log into device web interface. 3. Navigate to firmware update section. 4. Upload and apply new firmware. 5. Device will reboot automatically.

🔧 Temporary Workarounds

Disable Remote Management

all

Disable web management interface from being accessible over network

Login to device web interface
Navigate to Management Settings
Disable 'Remote Management' or 'Web Management'
Apply changes

Network Segmentation

all

Isolate device on separate VLAN with restricted access

Configure firewall rules to block external access to device management ports (typically 80/443)
Create separate VLAN for IoT/mobile devices
Implement strict egress filtering

🧯 If You Can't Patch

  • Isolate device on separate network segment with no access to critical systems
  • Implement strict firewall rules blocking all external access to device management interface

🔍 How to Verify

Check if Vulnerable:

Check firmware version in web interface (typically http://192.168.0.1 or http://192.168.1.1). If version is BD_R218V2.4 or earlier, device is vulnerable.

Check Version:

curl -s http://192.168.0.1/ | grep -i 'firmware version' or check web interface System Information page

Verify Fix Applied:

After firmware update, verify version shows BD_R218V2.5 or later in web interface. Test that command injection attempts no longer succeed.

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution in system logs
  • Multiple failed login attempts to web interface
  • Unexpected firmware modification attempts

Network Indicators:

  • Unusual outbound connections from device
  • Traffic to known malicious IPs
  • Port scanning originating from device

SIEM Query:

source="zte-mf920" AND (event="command_execution" OR event="firmware_modification")

🔗 References

📤 Share & Export