CVE-2024-7120

6.3 MEDIUM

📋 TL;DR

This critical vulnerability allows remote attackers to execute arbitrary operating system commands on affected Raisecom gateway devices by manipulating the 'template' parameter in the web interface. Attackers can gain full control of vulnerable devices without authentication. All organizations using Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 devices with version 3.90 are affected.

💻 Affected Systems

Products:
  • Raisecom MSG1200
  • Raisecom MSG2100E
  • Raisecom MSG2200
  • Raisecom MSG2300
Versions: Version 3.90
Operating Systems: Embedded OS on Raisecom devices
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the web interface component specifically in list_base_config.php file. 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, deploy ransomware, steal credentials, or establish persistent backdoors.

🟠

Likely Case

Device takeover leading to network disruption, data exfiltration, or use as a foothold for lateral movement.

🟢

If Mitigated

Limited impact if devices are isolated in separate VLANs with strict network segmentation and egress filtering.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and public exploits exist, making internet-facing devices immediate targets.
🏢 Internal Only: HIGH - Even internally, attackers who gain network access can exploit this to pivot through the network.

🎯 Exploit Status

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

Exploit details have been publicly disclosed and require minimal technical skill to execute. The attack can be initiated remotely without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available at time of analysis

Restart Required: No

Instructions:

1. Monitor Raisecom vendor website for security advisories. 2. Apply any available firmware updates immediately. 3. If no patch is available, implement workarounds and monitor for updates.

🔧 Temporary Workarounds

Disable Web Interface

all

Disable the vulnerable web interface component if not required for operations

# Access device CLI and disable web interface
# Configuration commands vary by device model

Network Access Control

linux

Restrict access to device web interface using firewall rules

# Example iptables rule to restrict web interface access
iptables -A INPUT -p tcp --dport 80 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j DROP

🧯 If You Can't Patch

  • Isolate affected devices in separate VLAN with strict egress filtering
  • Implement network-based intrusion detection rules to detect exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check device firmware version via web interface or CLI. If version is 3.90 on affected models, device is vulnerable.

Check Version:

# Via CLI: show version | include Software
# Via web: Navigate to System Information page

Verify Fix Applied:

Verify firmware version has been updated to a version later than 3.90, or that web interface is disabled/restricted.

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution in system logs
  • Multiple failed login attempts followed by successful access
  • Web interface access from unexpected IP addresses

Network Indicators:

  • HTTP requests to list_base_config.php with suspicious template parameters
  • Outbound connections from gateway devices to unexpected destinations

SIEM Query:

source="gateway_logs" AND (uri="*list_base_config.php*" AND param="*template=*" AND (param="*;*" OR param="*|*" OR param="*`*"))

🔗 References

📤 Share & Export