CVE-2018-17558

9.8 CRITICAL

📋 TL;DR

This CVE describes two critical vulnerabilities in ABUS security cameras: hardcoded manufacturer credentials and an OS command injection flaw in the /cgi-bin/mft/ directory. Attackers can exploit these to execute arbitrary code with root privileges on affected devices. Organizations using the listed ABUS camera models are at risk.

💻 Affected Systems

Products:
  • ABUS TVIP20050
  • ABUS TVIP10051
  • ABUS TVIP11050
  • ABUS TVIP20550
  • ABUS TVIP10050
  • ABUS TVIP11550
  • ABUS TVIP21050
  • ABUS TVIP51550
Versions: LM.1.6.18, MG.1.6.03.05, MG.1.6.03
Operating Systems: Embedded Linux
Default Config Vulnerable: ⚠️ Yes
Notes: All default configurations are vulnerable. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote attackers gain full root access to cameras, enabling complete device compromise, data exfiltration, lateral movement into networks, and persistent backdoor installation.

🟠

Likely Case

Attackers exploit cameras to create botnet nodes, conduct surveillance, or pivot to internal networks from internet-facing devices.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to isolated camera systems without critical data access.

🌐 Internet-Facing: HIGH - These are internet-connected security cameras with unauthenticated remote code execution, making them prime targets for mass exploitation.
🏢 Internal Only: MEDIUM - Internal exploitation still possible via network access, but requires attacker presence on internal network.

🎯 Exploit Status

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

Exploitation is trivial with publicly available proof-of-concept code. The hardcoded credentials bypass authentication, and command injection requires minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: No official vendor advisory available

Restart Required: No

Instructions:

No official patch exists. Manufacturer appears unresponsive based on references. Consider replacing affected devices.

🔧 Temporary Workarounds

Network Isolation

all

Place cameras on isolated VLAN with no internet access and strict firewall rules

Access Control

all

Block external access to camera web interfaces and restrict internal access to management networks only

🧯 If You Can't Patch

  • Immediately disconnect affected cameras from internet and place behind strict firewall
  • Replace affected cameras with patched models from different vendors if possible

🔍 How to Verify

Check if Vulnerable:

Check camera model and firmware version via web interface. If matches affected list, assume vulnerable.

Check Version:

Connect to camera web interface and check System Information or About page

Verify Fix Applied:

No fix available to verify. Only verification is device replacement with non-vulnerable model.

📡 Detection & Monitoring

Log Indicators:

  • Unusual authentication attempts
  • Unexpected process execution in camera logs
  • Access to /cgi-bin/mft/ directory

Network Indicators:

  • Outbound connections from cameras to unknown IPs
  • Unusual traffic patterns from camera IPs
  • Exploit kit traffic targeting camera IPs

SIEM Query:

source="camera_logs" AND (uri="/cgi-bin/mft/*" OR process="unexpected_command")

🔗 References

📤 Share & Export