CVE-2020-10176

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary commands on Yale WIPC-301W IP cameras through eval injection. Attackers can gain full control of affected devices, potentially compromising camera feeds and using devices as network footholds. All users of affected Yale camera versions are at risk.

💻 Affected Systems

Products:
  • ASSA ABLOY Yale WIPC-301W IP Camera
Versions: 2.x.2.29 through 2.x.2.43_p1
Operating Systems: Embedded Linux
Default Config Vulnerable: ⚠️ Yes
Notes: All devices running affected firmware versions are vulnerable out-of-the-box.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device takeover allowing attackers to view/record camera feeds, pivot to internal networks, install persistent malware, or use devices in botnets.

🟠

Likely Case

Unauthorized access to camera feeds, device compromise for surveillance or data exfiltration, and potential lateral movement within networks.

🟢

If Mitigated

Limited impact if devices are isolated on separate VLANs with strict network segmentation and access controls.

🌐 Internet-Facing: HIGH - Directly exposed devices can be remotely exploited without authentication.
🏢 Internal Only: HIGH - Even internally, devices can be exploited by attackers who gain network access.

🎯 Exploit Status

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

Exploitation requires network access to device but no authentication. Public proof-of-concept demonstrates remote code execution.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.x.2.44 and later

Vendor Advisory: https://www.assaabloy.com/en/com/our-brands/yale/cybersecurity

Restart Required: Yes

Instructions:

1. Check current firmware version via web interface. 2. Download latest firmware from Yale support portal. 3. Upload firmware via web interface. 4. Reboot device after update completes.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate cameras on separate VLAN with strict firewall rules blocking all inbound traffic except from management systems.

Access Control Lists

all

Implement IP-based access restrictions to limit which systems can communicate with cameras.

🧯 If You Can't Patch

  • Remove devices from internet exposure and place behind VPN with strict access controls
  • Implement network monitoring for suspicious traffic to/from camera devices

🔍 How to Verify

Check if Vulnerable:

Access camera web interface, navigate to System > Information, check firmware version. If version is between 2.x.2.29 and 2.x.2.43_p1, device is vulnerable.

Check Version:

curl -s http://[CAMERA_IP]/cgi-bin/version.cgi | grep firmware

Verify Fix Applied:

After update, verify firmware version shows 2.x.2.44 or higher in System > Information page.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to CGI endpoints
  • Multiple failed authentication attempts followed by successful access
  • System log entries showing unexpected process execution

Network Indicators:

  • Unusual outbound connections from camera devices
  • Traffic to known malicious IPs from camera
  • Unexpected port scanning originating from camera

SIEM Query:

source="camera_logs" AND (uri_path="*.cgi" AND method="POST" AND status="200") AND NOT user_agent="YaleBrowser"

🔗 References

📤 Share & Export