CVE-2025-55115
📋 TL;DR
A path traversal vulnerability in Control-M/Agent allows local attackers to escalate privileges on systems running affected versions. This impacts users with access to the system running the Agent, particularly in out-of-support versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions.
💻 Affected Systems
- BMC Control-M/Agent
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Full system compromise with root/admin privileges, allowing complete control over the affected system and potential lateral movement.
Likely Case
Local privilege escalation from a lower-privileged user to SYSTEM/root, enabling installation of malware, data theft, or persistence mechanisms.
If Mitigated
Limited impact if proper access controls restrict local user access and the system is isolated from critical resources.
🎯 Exploit Status
Requires local access to the system. Path traversal vulnerabilities typically have low exploitation complexity once the attack vector is identified.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 9.0.20.100 and above
Vendor Advisory: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441969
Restart Required: Yes
Instructions:
1. Upgrade to Control-M/Agent version 9.0.20.100 or later. 2. Download the patch from BMC support portal. 3. Follow BMC's upgrade documentation for your environment. 4. Restart the Control-M/Agent service after installation.
🔧 Temporary Workarounds
Restrict local user access
allLimit which users have local access to systems running Control-M/Agent
Implement strict file permissions
linuxSet restrictive permissions on Control-M/Agent directories and files
chmod 750 /opt/controlm/agent/*
chown root:controlm /opt/controlm/agent/*
🧯 If You Can't Patch
- Isolate affected systems from critical network segments and resources
- Implement strict monitoring and alerting for privilege escalation attempts
🔍 How to Verify
Check if Vulnerable:
Check Control-M/Agent version: If version is between 9.0.18 and 9.0.20 (excluding 9.0.20.100+), the system is vulnerable.Check Version:
On Linux: cat /opt/controlm/agent/version.txt or check Control-M Enterprise Manager interfaceVerify Fix Applied:
Verify version is 9.0.20.100 or higher and check that path traversal attempts are blocked.📡 Detection & Monitoring
Log Indicators:
- Unusual file access patterns in Control-M logs
- Failed or successful privilege escalation attempts
- Access to sensitive system directories by Control-M processes
Network Indicators:
- N/A - Local vulnerability only
SIEM Query:
source="controlm" AND (event_type="file_access" OR event_type="privilege_escalation") AND (path="..\\" OR path="../")