CVE-2025-29269

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary operating system commands on ALLNET ALL-RUT22GW industrial LTE cellular routers via the popen.cgi endpoint. Attackers can gain complete control of affected devices without authentication. Organizations using these routers in industrial, IoT, or network infrastructure deployments are at risk.

💻 Affected Systems

Products:
  • ALLNET ALL-RUT22GW Industrial LTE Cellular Router
Versions: v3.3.8 (specific version mentioned; earlier versions may also be affected)
Operating Systems: Embedded Linux-based firmware
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default web interface configuration. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device compromise allowing attackers to pivot to internal networks, intercept/modify traffic, deploy ransomware, or use devices as botnet nodes for DDoS attacks.

🟠

Likely Case

Attackers gain root access to routers, enabling traffic interception, credential theft, network reconnaissance, and persistence for future attacks.

🟢

If Mitigated

With proper network segmentation and access controls, impact limited to isolated network segments, though device compromise still occurs.

🌐 Internet-Facing: HIGH - Routers are typically deployed at network perimeters with internet-facing interfaces, making them directly accessible to attackers.
🏢 Internal Only: MEDIUM - If routers are deployed internally only, risk reduces but still significant due to command injection vulnerability.

🎯 Exploit Status

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

The vulnerability requires no authentication and can be exploited with simple HTTP requests containing command injection payloads.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available at time of analysis

Restart Required: No

Instructions:

1. Monitor ALLNET website for security advisories. 2. Check for firmware updates via router web interface. 3. Apply any available patches immediately.

🔧 Temporary Workarounds

Block popen.cgi endpoint

linux

Use firewall rules or web server configuration to block access to the vulnerable endpoint

iptables -A INPUT -p tcp --dport 80 -m string --string "popen.cgi" --algo bm -j DROP
iptables -A INPUT -p tcp --dport 443 -m string --string "popen.cgi" --algo bm -j DROP

Disable web interface

all

Disable the router's web management interface if not required

Check router configuration for web interface disable option

🧯 If You Can't Patch

  • Segment routers on isolated VLANs with strict firewall rules limiting inbound/outbound traffic
  • Implement network monitoring with IDS/IPS rules to detect command injection attempts

🔍 How to Verify

Check if Vulnerable:

Test by sending HTTP request to http://[router-ip]/popen.cgi?command=id and checking for command output in response

Check Version:

Check router web interface or use curl -s http://[router-ip]/cgi-bin/version.cgi

Verify Fix Applied:

Verify patch by testing same exploit attempt and confirming command execution fails

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests to popen.cgi with suspicious parameters
  • Unusual command execution in system logs
  • Multiple failed login attempts followed by popen.cgi access

Network Indicators:

  • HTTP requests containing shell metacharacters (;, |, &, $, `)
  • Unusual outbound connections from router to unknown IPs
  • Traffic patterns suggesting command-and-control communication

SIEM Query:

source="router_logs" AND (url="*popen.cgi*" AND (param="*;*" OR param="*|*" OR param="*&*" OR param="*`*" OR param="*$*"))

🔗 References

📤 Share & Export