CVE-2024-56131

8.4 HIGH

📋 TL;DR

An authenticated user can execute arbitrary operating system commands on Progress LoadMaster due to improper input validation. This affects LoadMaster, Multi-Tenant Hypervisor, and ECS products across multiple vulnerable versions. Attackers with valid credentials can potentially gain full system control.

💻 Affected Systems

Products:
  • LoadMaster
  • Multi-Tenant Hypervisor
  • ECS
Versions: LoadMaster: 7.2.55.0 to 7.2.60.1, 7.2.49.0 to 7.2.54.12, 7.2.48.12 and prior; Multi-Tenant Hypervisor: 7.1.35.12 and prior; ECS: All versions prior to 7.2.60.1
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user access. All affected versions in default configuration are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to execute arbitrary commands, steal sensitive data, deploy ransomware, or pivot to other network systems.

🟠

Likely Case

Authenticated attackers gaining shell access to the LoadMaster system, potentially modifying configurations, intercepting traffic, or installing backdoors.

🟢

If Mitigated

Limited impact if strong authentication controls, network segmentation, and command execution restrictions are properly implemented.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires authenticated access. Attack complexity is medium due to authentication requirement but command injection is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: LoadMaster 7.2.60.2 or later; Multi-Tenant Hypervisor 7.1.35.13 or later; ECS 7.2.60.2 or later

Vendor Advisory: https://community.progress.com/s/article/LoadMaster-Security-Vulnerability-CVE-2024-56131-CVE-2024-56132-CVE-2024-56133-CVE-2024-56134-CVE-2024-56135

Restart Required: No

Instructions:

1. Backup current configuration. 2. Download latest firmware from Progress support portal. 3. Apply firmware update through LoadMaster web interface. 4. Verify update completed successfully.

🔧 Temporary Workarounds

Restrict User Access

all

Limit authenticated user accounts to only essential personnel and implement strong authentication controls.

Network Segmentation

all

Isolate LoadMaster systems from critical network segments and implement strict firewall rules.

🧯 If You Can't Patch

  • Implement strict access controls and multi-factor authentication for all LoadMaster administrative accounts
  • Deploy network-based intrusion detection systems to monitor for command injection attempts and unusual system commands

🔍 How to Verify

Check if Vulnerable:

Check current LoadMaster version via web interface: System Configuration > System Administration > System Information

Check Version:

ssh admin@loadmaster-ip 'cat /etc/version' or check web interface

Verify Fix Applied:

Verify version is 7.2.60.2 or later for LoadMaster, 7.1.35.13 or later for Multi-Tenant Hypervisor, or 7.2.60.2 or later for ECS

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution in system logs
  • Multiple failed authentication attempts followed by successful login
  • Unexpected system process creation

Network Indicators:

  • Unusual outbound connections from LoadMaster system
  • Traffic patterns inconsistent with normal load balancing operations

SIEM Query:

source="loadmaster" AND (event_type="command_execution" OR process_name="sh" OR process_name="bash")

🔗 References

📤 Share & Export