CVE-2025-55109
BMC Control-M/Agent default SSL/TLS configuration authenticated bypass
Description
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.
INFO
Published Date :
Sept. 16, 2025, 12:14 p.m.
Last Modified :
Sept. 16, 2025, 12:14 p.m.
Remotely Exploit :
Yes !
Source :
airbus
Affected Products
The following products are affected by CVE-2025-55109
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | 24a3c815-5f22-4d74-967a-30958d6466f4 | ||||
| CVSS 4.0 | CRITICAL | 24a3c815-5f22-4d74-967a-30958d6466f4 |
Solution
- Upgrade Control-M/Agent to a supported version.
- Replace expired certificates with valid ones.
- Configure agent with a properly managed keystore.
- Securely manage trusted certificates.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-55109 vulnerability anywhere in the article.