CVE-2025-55109: BMC Control-M/Agent default SSL/TLS configuration authenticated bypass
An authentication bypass vulnerability exists in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions when using an empty or default kdb keystore or a default PKCS#12 keystore. A remote attacker with access to a signed third-party or demo certificate for client authentication can bypass the need for a certificate signed by the certificate authority of the organization during authentication on the Control-M/Agent.
The Control-M/Agent contains hardcoded certificates which are only trusted as fallback if an empty kdb keystore is used; they are never trusted if a PKCS#12 keystore is used. All of these certificates are now expired.
In addition, the Control-M/Agent default kdb and PKCS#12 keystores contain trusted third-party certificates (external recognized CAs and default self-signed demo certificates) which are trusted for client authentication.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-55109?
CVE-2025-55109 is classified as a high severity vulnerability due to its potential for authentication bypass.
How do I fix CVE-2025-55109?
To fix CVE-2025-55109, users should upgrade to a supported version of BMC Control-M/Agent that is not affected by this vulnerability.
What versions of BMC Control-M/Agent are affected by CVE-2025-55109?
CVE-2025-55109 affects BMC Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions.
What type of vulnerability is CVE-2025-55109?
CVE-2025-55109 is an authentication bypass vulnerability that can be exploited by remote attackers.
Are there any workarounds for CVE-2025-55109?
There are no specific workarounds documented for CVE-2025-55109 other than upgrading to a secure version.