Control-M

Control-M 9.0.21

Control-M 9.0.21

Third-party support for the Control-M 9.0.21: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance — independent of the vendor contract.

EOSL Date: Sep 8, 2027
Issue Management

24/7 engineers own your Control-M 9.0.21 incidents end to end.

Vulnerability Remediation

Mitigation and patch-around guidance when the vendor no longer ships fixes.

Compliance Maintenance

Controls evidence and documentation that keep auditors satisfied.

Specifications

product
controlm
release
9.0.21
product Label
Control-M
release Label
9.0.21
codename
lts
latest Version
9.0.21.300
release Date
2022-09-08
maintained
true
source Url
https://endoflife.date/controlm

Lifecycle Dates

End of Service Life
Sep 8, 2027
Last OEM Support
Sep 30, 2026

Get Third Party Support

Your quote will be sent to this address.

By submitting this form, you agree to our Privacy Policy.

OEM vs. 3rd Party Support

See how third-party support compares to the vendor contract for Control-M 9.0.21 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.

FeatureOEM Support3rd 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.21?

Vulnerability Remediation

Scanning, mitigation and patch-around guidance for Control-M 9.0.21 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.21 Support: Frequently Asked Questions

Is the Control-M 9.0.21 still supported?

Yes. The Control-M 9.0.21 is currently supported by Control-M, and third-party support is available as an alternative — issue management, vulnerability remediation, and compliance help independent of the vendor contract.

When is the Control-M 9.0.21 end of service life (EOSL) date?

Control-M lists the end of service life for the Control-M 9.0.21 as Sep 8, 2027.

Can I keep using the Control-M 9.0.21 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.21 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.21

3 published CVEs affect the Control-M 9.0.21. Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.

CVESeverityCVSSPublishedSummary
CVE-2024-1605MEDIUM6.6Mar 18, 2024BMC 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-1604MEDIUM6.4Mar 18, 2024Improper 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-1606MEDIUM4.6Mar 18, 2024Lack 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.
Get Third Party Support

Related Control-M Products

All Control-M products →
Control-M 9.0.21
Save 40-70% vs OEM
Get Third Party Support