CVE-2025-55108: fallo crítico en BMC Control-M/Agent
BMC Control-M/Agent default configuration does not enforce SSL/TLS allowing unauthorized actions and remote code execution
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
28Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 9.5epss 0.8%
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
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Productos afectados
BMC · Control-M/AgentCVEs relacionadas — BMC Control-M/Agent
En el mismo producto, de las más peligrosas a las menos.
CVE-2025-55114MEDIUMBMC Control-M/Agent improper IP address filtering orderEPSS 0.4%CVE-2025-55118HIGHBMC Control-M/Agent memory corruption in SSL/TLS communicationEPSS 0.4%CVE-2025-55109CRITICALBMC Control-M/Agent default SSL/TLS configuration authenticated bypassEPSS 0.4%CVE-2025-55117MEDIUMBMC Control-M/Agent buffer overflow in SSL/TLS communicationEPSS 0.3%CVE-2025-55113CRITICALBMC Control-M/Agent unescaped NULL byte in access control list checksEPSS 0.3%CVE-2025-55112HIGHBMC Control-M/Agent hardcoded Blowfish keysEPSS 0.2%