CVE-2025-45988

9.8 CRITICAL

📋 TL;DR

This CVE describes multiple command injection vulnerabilities in Blink routers where attackers can execute arbitrary commands via the cmd parameter in the bs_SetCmd function. The vulnerability affects multiple Blink router models and firmware versions, allowing remote code execution with high impact. Anyone using the affected router models with vulnerable firmware versions is at risk.

💻 Affected Systems

Products:
  • Blink BL-WR9000
  • Blink BL-AC2100_AZ3
  • Blink BL-X10_AC8
  • Blink BL-LTE300
  • Blink BL-F1200_AT1
  • Blink BL-X26_AC8
  • Blink BLAC450M_AE4
  • Blink BL-X26_DA3
Versions: V2.4.9, V1.0.4, v1.0.5, v1.2.3, v1.0.0, v1.2.8, v4.0.0, v1.2.7 respectively
Operating Systems: Embedded router firmware
Default Config Vulnerable: ⚠️ Yes
Notes: All listed firmware versions are vulnerable. The vulnerability exists in the web interface/management functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the router allowing attackers to execute arbitrary commands, pivot to internal networks, intercept traffic, install persistent backdoors, and use the device for botnet activities.

🟠

Likely Case

Remote attackers gaining shell access to the router, modifying configurations, intercepting network traffic, and potentially compromising connected devices.

🟢

If Mitigated

Limited impact if routers are behind firewalls with strict inbound filtering and network segmentation prevents lateral movement.

🌐 Internet-Facing: HIGH - Routers are typically internet-facing devices, and the vulnerability allows unauthenticated remote exploitation.
🏢 Internal Only: MEDIUM - While less likely to be exploited from internal networks, the vulnerability still exists and could be leveraged in lateral movement attacks.

🎯 Exploit Status

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

The GitHub reference contains technical details about the vulnerability, making exploitation straightforward for attackers with basic skills.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: Yes

Instructions:

1. Check Blink vendor website for security advisories. 2. If patches are available, download the latest firmware. 3. Backup current router configuration. 4. Upload and apply the new firmware through the web interface. 5. Verify the update was successful and reconfigure if necessary.

🔧 Temporary Workarounds

Network Segmentation and Access Control

all

Isolate affected routers in separate network segments and restrict management interface access

Firewall Rules to Block Management Interface

linux

Configure firewall to block external access to router management interfaces

iptables -A INPUT -p tcp --dport 80 -j DROP
iptables -A INPUT -p tcp --dport 443 -j DROP
iptables -A INPUT -p tcp --dport 8080 -j DROP

🧯 If You Can't Patch

  • Replace affected routers with different models that don't have this vulnerability
  • Implement strict network monitoring and intrusion detection for suspicious router traffic patterns

🔍 How to Verify

Check if Vulnerable:

Check router firmware version in web interface under System Status or About sections. Compare against affected versions list.

Check Version:

Login to router web interface and navigate to System Status or About page to view firmware version.

Verify Fix Applied:

After patching, verify firmware version has changed to a non-vulnerable version. Test management interface functionality remains intact.

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution in router logs
  • Multiple failed login attempts followed by successful access
  • Unexpected configuration changes

Network Indicators:

  • Unusual outbound connections from router
  • Traffic patterns inconsistent with normal router operation
  • Port scanning originating from router

SIEM Query:

source="router_logs" AND (cmd="*;*" OR cmd="*|*" OR cmd="*`*" OR cmd="*$(*)")

🔗 References

📤 Share & Export