CVE-2025-55117 in Control-M
Summary
by MITRE • 09/16/2025
A stack-based buffer overflow can be remotely triggered when formatting an error message in the Control-M/Agent when SSL/TLS communication is configured.
The issue occurs in the following cases:
* Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting "use_openssl=n"; * Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings "JAVA_AR=N" and "use_openssl=n".
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 09/16/2025
This vulnerability represents a critical stack-based buffer overflow condition that can be remotely exploited through specially crafted error message formatting operations within the Control-M/Agent software. The flaw specifically manifests when SSL/TLS communication is configured, creating a pathway for remote attackers to execute arbitrary code on affected systems. The vulnerability is particularly concerning as it affects multiple versions of the Control-M/Agent software, including 9.0.20, 9.0.21, and 9.0.22, each with their own specific configuration requirements that must be met for the exploit to succeed. The technical implementation involves improper bounds checking during error message formatting operations, where attacker-controlled input is processed without adequate validation mechanisms, leading to memory corruption that can be leveraged for privilege escalation or system compromise.
The operational impact of this vulnerability extends beyond simple remote code execution as it represents a significant threat to enterprise automation environments where Control-M/Agent serves as a critical component for job scheduling and workflow management. Organizations utilizing these specific versions with the mentioned non-default configurations face potential exposure to sophisticated attack campaigns targeting their automation infrastructure. The vulnerability's remote exploitability means that attackers can potentially compromise systems without requiring physical access or prior authentication, making it particularly dangerous in environments where network segmentation may not be comprehensive. Attackers could leverage this flaw to gain unauthorized access to sensitive job scheduling data, manipulate automated workflows, or establish persistent access points within enterprise networks that rely heavily on Control-M for critical business operations.
Security mitigations for this vulnerability should focus on immediate patch deployment as provided by the vendor, while organizations should also implement network segmentation controls to limit access to affected systems. The configuration requirements for exploitation indicate that organizations should review their SSL/TLS and agent router settings to ensure they are not using the vulnerable non-default configurations. Additionally, implementing intrusion detection systems with signatures for this specific vulnerability can help identify exploitation attempts. From a compliance perspective, this vulnerability aligns with CWE-121 stack-based buffer overflow conditions and represents a significant risk under frameworks such as NIST SP 800-53 controls for system security and vulnerability management. Organizations should also consider implementing the principle of least privilege for Control-M/Agent services and establishing monitoring procedures for unusual error message formatting activities that could indicate exploitation attempts. The ATT&CK framework would categorize this vulnerability under T1203 Exploitation for Client Execution and potentially T1071.004 Application Layer Protocol: DNS, depending on how attackers might establish initial access to the vulnerable systems.