CRITICAL CVSS 9.0
Published: 2025-09-16

CVE-2025-55109

bmc control-m\/agent Security Advisory (CVE-2025-55109)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-55109?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-55109 impacting bmc control-m\/agent. Evaluated with CVSS Base Score of 9.0 (CRITICAL).

Original NVD Description

Source: NIST NVD
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.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
High (AC:H)
Depends on race conditions or environment
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product bmc / control-m\/agent
Affected Versions *
Weakness Enumeration CWE-295

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-55109 impacting bmc control-m\/agent.

⚡ Nuclei Detection Template (YAML) cve-2025-55109.yaml
id: cve-2025-55109

info:
  name: bmc control-m\/agent - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2025-55109 affecting bmc control-m\/agent.
    Evaluation: 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 vers...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-55109
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 9.0
    cve-id: CVE-2025-55109
    cwe-id: CWE-295
  tags: cve,cve-2025-55109,bmc,control-m\/agent,critical

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "control-m\/agent"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-55109.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-55109
# Target: bmc control-m\/agent | CVSS: 9.0 (CRITICAL)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-55109 (bmc control-m\/agent)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against bmc control-m\/agent scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-55109.sh
# Recommended Remediation & Patching Commands for CVE-2025-55109
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install control-m\/agent 2>/dev/null || \
sudo dnf upgrade control-m\/agent 2>/dev/null || \
sudo yum update control-m\/agent

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i control-m\/agent 2>/dev/null || rpm -qa | grep -i control-m\/agent

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-55109 in bmc control-m\/agent?

Review vendor-specific security notices and update bmc control-m\/agent packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-55109?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-55109?

CVE-2025-55109 is classified with a CVSS 3.1 Base Score of 9.0 (CRITICAL). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
9.0
CRITICAL SEVERITY
CVE ID CVE-2025-55109
Weakness CWE-295
Vendor bmc
Product control-m\/agent
Published 2025-09-16
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H