CVE-2024-37187

5.7 MEDIUM

📋 TL;DR

Advantech ADAM-5550 industrial controllers store and transmit user credentials using only base64 encoding, which provides no meaningful encryption. This allows attackers who gain access to the system or network traffic to easily decode and steal credentials. Organizations using these industrial control systems in manufacturing, energy, or infrastructure sectors are affected.

💻 Affected Systems

Products:
  • Advantech ADAM-5550
Versions: All versions prior to patched firmware
Operating Systems: Embedded firmware
Default Config Vulnerable: ⚠️ Yes
Notes: All default configurations are vulnerable as base64 encoding of credentials is the default storage method.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers obtain administrative credentials, gain full control of industrial controllers, manipulate industrial processes, cause physical damage, or disrupt critical operations.

🟠

Likely Case

Attackers with network access steal credentials, gain unauthorized access to industrial control systems, and potentially disrupt operations or conduct reconnaissance for further attacks.

🟢

If Mitigated

With proper network segmentation and access controls, attackers cannot reach the vulnerable systems, limiting exposure to internal threats only.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires network access to the device or access to stored credential files. Base64 decoding is trivial and widely available in all programming languages.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Advantech advisory for specific firmware version

Vendor Advisory: https://www.advantech.com/support/details/firmware?id=1OEL9S00V0

Restart Required: Yes

Instructions:

1. Download latest firmware from Advantech support portal. 2. Backup current configuration. 3. Upload new firmware via web interface. 4. Restart device. 5. Verify credentials are now properly encrypted.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate ADAM-5550 controllers in dedicated industrial network segments with strict firewall rules

Credential Rotation

all

Change all passwords on affected devices to reduce impact if credentials are compromised

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can communicate with ADAM-5550 devices
  • Monitor network traffic to/from these devices for credential extraction attempts

🔍 How to Verify

Check if Vulnerable:

Check if credentials in configuration files or network traffic appear as base64 encoded strings (typically ending with = or == padding)

Check Version:

Check firmware version via web interface at http://[device-ip]/status or via serial console

Verify Fix Applied:

After patching, verify credentials are no longer stored or transmitted as base64 encoded plaintext

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed login attempts
  • Unauthorized configuration changes
  • Unexpected credential access

Network Indicators:

  • Base64 encoded strings in network traffic to/from port 80/443 of ADAM-5550
  • Credential extraction patterns

SIEM Query:

source_ip=[ADAM-5550_IP] AND (http_content CONTAINS "base64" OR packet_payload MATCHES "[A-Za-z0-9+/=]{20,}")

🔗 References

📤 Share & Export