Control-M 9.0.20
Control-M 9.0.20
The Control-M 9.0.20 reached end of service life on Jul 23, 2025 — Control-M no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Control-M 9.0.20 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- controlm
- release
- 9.0.20
- product Label
- Control-M
- release Label
- 9.0.20
- codename
- lts
- latest Version
- 9.0.20.200
- release Date
- 2020-07-24
- maintained
- source Url
- https://endoflife.date/controlm
Lifecycle Dates
- End of Service Life
- Jul 23, 2025
- Last OEM Support
- Apr 30, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Control-M 9.0.20 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Control-M 9.0.20?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Control-M 9.0.20 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Control-M 9.0.20 Support: Frequently Asked Questions
Is the Control-M 9.0.20 still supported?
Control-M ended support for the Control-M 9.0.20 on Jul 23, 2025 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Control-M 9.0.20 end of service life (EOSL) date?
Control-M lists the end of service life for the Control-M 9.0.20 as Jul 23, 2025.
Can I keep using the Control-M 9.0.20 after its EOSL date?
Yes. EOSL means Control-M stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Control-M 9.0.20 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Control-M 9.0.20
5 published CVEs affect the Control-M 9.0.20, including 2 rated critical or high severity. Control-M no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-39122 | CRITICAL | 9.8 | Jul 31, 2023 | BMC Control-M through 9.0.20.200 allows SQL injection via the /RF-Server/report/deleteReport report-id parameter. This is fixed in 9.0.21 (and is also fixed by a patch for 9.0.20.200). |
| CVE-2023-26550 | CRITICAL | 9.8 | Feb 25, 2023 | A SQL injection vulnerability in BMC Control-M before 9.0.20.214 allows attackers to execute arbitrary SQL commands via the memname JSON field. |
| CVE-2024-1605 | MEDIUM | 6.6 | Mar 18, 2024 | BMC Control-M branches 9.0.20 and 9.0.21 upon user login load all Dynamic Link Libraries (DLL) from a directory that grants Write and Read permissions to all users. Leveraging it leads to loading of a potentially malicious libraries, which will execute with the application's privileges. 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.201. |
| CVE-2024-1604 | MEDIUM | 6.4 | Mar 18, 2024 | Improper authorization in the report management and creation module of BMC Control-M branches 9.0.20 and 9.0.21 allows logged-in users to read and make unauthorized changes to any reports available within the application, even without proper permissions. The attacker must know the unique identifier of the report they want to manipulate. 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.201. |
| CVE-2024-1606 | MEDIUM | 4.6 | Mar 18, 2024 | 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. |