BMC Control-M/Agent default configuration does not enforce SSL/TLS allowing unauthorized actions and remote code execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| BMC | Control-M/Agent | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Bmc | Control-m/agent | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.825% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Control-M/Agent is vulnerable to unauthenticated remote code execution, arbitrary file read and write and similar unauthorized actions when mutual SSL/TLS authentication is not enabled (i.e. in the default configuration). NOTE: The vendor believes that this vulnerability only occurs when documented security best practices are not followed. BMC has always strongly recommended to use security best practices such as configuring SSL/TLS between Control-M Server and Agent. | The Control-M/Agent is vulnerable to unauthenticated remote code execution, arbitrary file read and write and similar unauthorized actions when mutual SSL/TLS authentication is not enabled (i.e. in the default configuration). NOTE: * The vendor believes that this vulnerability only occurs when documented security best practices are not followed. BMC has always strongly recommended to use security best practices such as configuring SSL/TLS between Control-M Server and Agent. * The vendor notifies that Control-M/Agent is not impacted in Control-M SaaS |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bmc
Bmc control-m/agent |
|
| Vendors & Products |
Bmc
Bmc control-m/agent |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Control-M/Agent is vulnerable to unauthenticated remote code execution, arbitrary file read and write and similar unauthorized actions when mutual SSL/TLS authentication is not enabled (i.e. in the default configuration). NOTE: The vendor believes that this vulnerability only occurs when documented security best practices are not followed. BMC has always strongly recommended to use security best practices such as configuring SSL/TLS between Control-M Server and Agent. | |
| Title | BMC Control-M/Agent default configuration does not enforce SSL/TLS allowing unauthorized actions and remote code execution | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|