dbcve.org
Control MApplication · Bmc

CVE-2024-1606

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 9.0.20.238 / 9.0.21.201 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Lack of input sanitization in BMC Control-M branches 9.0.20 and 9.0.21 allows logged-in users for manipulation of generated web pages via injection of HTML code. This might lead to a successful phishing attack for example by tricking users into using a hyperlink pointing to a website controlled by an attacker. Fix for 9.0.20 branch was released in version 9.0.20.238. Fix for 9.0.21 branch was released in version 9.0.21.200.

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 · high confidence

Stored XSS vulnerability in BMC Control-M web interface where authenticated users can inject arbitrary HTML/JavaScript into generated web pages due to lack of input sanitization. This allows malicious code to persist and execute in other users' browsers when viewing affected pages.

MitigationImplement context-aware output encoding and input validation across all user-supplied data fields in the web application to neutralize malicious HTML/JS payloads before rendering.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Control MApplication
Affected:>= 9.0.20, < 9.0.20.238>= 9.0.21, < 9.0.21.201

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
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installation
    Check for Control-M processes or services running on the system. Look for processes named 'ctm' or 'Control-M' in task manager or via command: tasklist | findstr -i ctm
    Affected if Control-M is not installed on this system - not vulnerable
  2. Determine Control-M version
    Check the installed version by inspecting the Control-M installation directory for version files, or query the web interface version via its about/help page typically accessible at /ControlM/ or /api/v1/version
    Affected if Version falls within 9.0.20.x (where x < 238) or 9.0.21.x (where x < 201) - system is potentially affected
  3. Verify web interface is enabled
    Confirm the Control-M web interface service is running and accessible. Test connectivity to typical web interface ports (8080, 8443, or configured ports) or check if the Control-M tomcat/web service is active
    Affected if Web interface is disabled or not accessible - exploitation is not possible in current configuration
  4. Confirm user authentication is configured
    Check if Control-M has user authentication enabled for the web interface by reviewing authentication settings in the Control-M configuration files or attempting to access the login page
    Affected if Web interface allows unauthenticated access - the specific authenticated XSS vector may not apply as described

System is affected if running Control-M version 9.0.20 through 9.0.20.237 OR 9.0.21 through 9.0.200 with the web interface enabled and user authentication 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.

dbcve · scoped
Upgrade available Upgrade to 9.0.20.238 / 9.0.21.201 or later
Fixed in 9.0.20.2389.0.21.201
Interim mitigation

Implement context-aware output encoding and input validation across all user-supplied data fields in the web application to neutralize malicious HTML/JS payloads before rendering.

Recommended fix High confidence

Control-M 9.0.20.238 or 9.0.21.200 (depending on current branch)

  1. Identify the currently installed Control-M version to determine which upgrade path is needed (9.0.20.x or 9.0.21.x)
  2. Review BMC Control-M upgrade documentation and release notes for the target fixed version
  3. For systems on 9.0.20 branch: plan upgrade to version 9.0.20.238
  4. For systems on 9.0.21 branch: plan upgrade to version 9.0.21.200
  5. Create a backup of the Control-M configuration and database
  6. Schedule maintenance window as upgrade may require downtime
  7. Execute the upgrade following BMC's official upgrade procedure
  8. Verify the upgrade completed successfully
Caveat Review BMC release notes for any configuration or behavioral changes between versions; some upgrades may require intermediate steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control M Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1606 — 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-2024-1606 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