CVE-2025-55118
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-11-18
Assigner: Airbus
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| bmc | control-m_agent | 9.0.22 |
| bmc | control-m_agent | 9.0.20 |
| bmc | control-m_agent | 9.0.21 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-665 | The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. |
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
| CWE-191 | The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. |
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-835 | The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. |
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-55118 is a vulnerability in Control-M/Agent versions 9.0.22 and lower where memory corruption can be triggered remotely during SSL/TLS communication. This happens when certain non-default SSL/TLS configurations are used, such as "use_openssl=n" or "JAVA_AR=N" combined with "use_openssl=n". The issue is due to improper handling within the SSL/TLS protocol implementation, which can cause memory corruption during secure communications. [1]
How can this vulnerability impact me? :
This vulnerability can lead to memory corruption remotely, which may be exploited by attackers to cause denial of service, crash the agent, or potentially execute arbitrary code. This impacts the security and stability of systems using affected Control-M/Agent versions with the specified SSL/TLS configurations. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that Control-M/Agent is not configured with the non-default SSL/TLS settings that trigger the issue. Specifically, avoid using 'use_openssl=n' in version 9.0.20, and avoid the combination of 'JAVA_AR=N' and 'use_openssl=n' in versions 9.0.21 and 9.0.22. Upgrading to a version higher than 9.0.22 or reverting to default SSL/TLS configurations is recommended. [1]