CVE-2019-6522

9.1 CRITICAL

📋 TL;DR

This vulnerability in Moxa IKS and EDS industrial switches allows attackers to read arbitrary device memory due to improper array bounds checking. Attackers can potentially retrieve sensitive data or cause device reboots, affecting organizations using these industrial networking devices.

💻 Affected Systems

Products:
  • Moxa IKS-G6824A Series
  • Moxa EDS-405A Series
  • Moxa EDS-408A Series
  • Moxa EDS-510A Series
Versions: Firmware versions prior to 3.8
Operating Systems: Embedded firmware
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

Complete device compromise allowing data exfiltration, denial of service, and potential lateral movement within industrial control systems.

🟠

Likely Case

Sensitive data leakage and device instability leading to operational disruption in industrial environments.

🟢

If Mitigated

Limited impact if devices are isolated and have proper network segmentation.

🌐 Internet-Facing: HIGH - Industrial devices often have web interfaces and may be exposed to internet.
🏢 Internal Only: MEDIUM - Still significant risk from internal threats or compromised systems.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires network access to device but no authentication. Memory reading requires specific knowledge of device architecture.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Firmware version 3.8

Vendor Advisory: https://www.moxa.com/en/support/product-support/security-advisory/moxa-iks-and-eds-series-industrial-ethernet-switches-vulnerabilities

Restart Required: Yes

Instructions:

1. Download firmware version 3.8 from Moxa website. 2. Backup current configuration. 3. Upload new firmware via web interface or CLI. 4. Reboot device. 5. Restore configuration if needed.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate affected devices in separate VLANs with strict firewall rules.

Access Control Lists

all

Implement ACLs to restrict access to device management interfaces.

access-list 100 deny ip any host <device_ip>
access-list 100 permit ip any any

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate devices from untrusted networks
  • Monitor network traffic to/from affected devices for unusual patterns

🔍 How to Verify

Check if Vulnerable:

Check firmware version via web interface (System > System Information) or CLI command 'show version'

Check Version:

show version

Verify Fix Applied:

Verify firmware version is 3.8 or later using same methods as checking vulnerability

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed memory access attempts
  • Unexpected device reboots
  • Unusual memory read patterns

Network Indicators:

  • Unusual traffic to device management ports (80, 443, 23)
  • Memory read requests to unusual addresses

SIEM Query:

source_ip=* AND dest_ip=<device_ip> AND (port=80 OR port=443 OR port=23) AND bytes_transferred>threshold

🔗 References

📤 Share & Export