dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-55118

HIGH · 8.9 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Memory corruptions can be remotely triggered in the Control-M/Agent when SSL/TLS communication is configured. The issue occurs in the following cases: * Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting "use_openssl=n"; * Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings "JAVA_AR=N" and "use_openssl=n"

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory corruption vulnerability in BMC Control-M/Agent's SSL/TLS communication handling. The flaw is triggered when specific non-default configuration settings are used: 'use_openssl=n' in version 9.0.20, and both 'JAVA_AR=N' combined with 'use_openssl=n' in versions 9.0.21 and 9.0.22. The vulnerability is remotely exploitable via network communication.

MitigationRevert SSL/TLS configuration to default settings (use_openssl should not be set to 'n'), or apply vendor patches for the affected Control-M/Agent versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Control-M/Agent version
    Run the command to check the installed Control-M/Agent version (typically via 'ctmversion' or inspecting version files in the Control-M installation directory)
    Affected if Version is 9.0.20, 9.0.21, or 9.0.22
  2. Locate configuration file with SSL settings
    Find the configuration file that contains the 'use_openssl' parameter (commonly in agent config files such as ctmagent.cfg, agent.cfg, or similar in the Control-M/Agent config directory)
    Affected if Configuration file exists and contains use_openssl setting
  3. Check use_openssl configuration value
    Inspect the value of 'use_openssl' in the configuration file - look for 'use_openssl=n' or 'use_openssl=N'
    Affected if use_openssl is set to 'n' or 'N'
  4. Check JAVA_AR configuration value (for versions 9.0.21 and 9.0.22)
    If version is 9.0.21 or 9.0.22, locate and inspect the 'JAVA_AR' parameter in the same or related configuration file - look for 'JAVA_AR=N'
    Affected if JAVA_AR is set to 'N' (only applies to versions 9.0.21 and 9.0.22)
  5. Confirm vulnerable configuration combination
    Review all identified settings together: for v9.0.20 check if use_openssl=n alone; for v9.0.21-9.0.22 check if both JAVA_AR=N and use_openssl=n are present
    Affected if Version 9.0.20 has use_openssl=n, OR version 9.0.21-9.0.22 has both JAVA_AR=N and use_openssl=n

Your environment is affected if running Control-M/Agent version 9.0.20 with use_openssl=n, or versions 9.0.21-9.0.22 with both JAVA_AR=N and use_openssl=n configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Revert SSL/TLS configuration to default settings (use_openssl should not be set to 'n'), or apply vendor patches for the affected Control-M/Agent versions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55118 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data