CVE-2024-1604
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 · uneditedImproper 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.
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 confidenceImproper authorization vulnerability in BMC Control-M's report management module allows authenticated users to access and modify any report by knowing its unique identifier, bypassing permission checks. This is an Insecure Direct Object Reference (IDOR) issue where the application fails to validate user permissions before allowing report access or modifications.
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>= 9.0.20, < 9.0.20.238>= 9.0.21, < 9.0.21.201CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Control-M versionRun the command 'ctmversion' or check the Control-M installation directory for version files. On Linux/Unix, try: /opt/control-m/ctm/version.txt or ctm --version. On Windows, check the registry or installation folder.Affected if The installed version is 9.0.20.x where x < 238, OR 9.0.21.x where x < 201, meaning it falls within the vulnerable version ranges.
-
Confirm report management module is in useCheck if the Control-M web interface (Control-M/EM) is accessible and the Reports module is available. Look for the 'Reports' or 'Report Manager' section in the Control-M interface or check configuration files in the installation directory for report module settings.Affected if The report management module is enabled and accessible to authenticated users.
-
Review user access permissions on reportsLog into Control-M as a standard (non-admin) user who has access to the report module. Attempt to access a report by directly modifying the report ID parameter in the URL or API request to reference a report owned by a different user. Observe whether the system returns the report content without authorization errors.Affected if The system returns report data or allows modifications to reports belonging to other users without proper authorization validation, indicating the IDOR vulnerability is present.
-
Check for audit logs indicating unauthorized report accessExamine Control-M audit logs or security logs in the Control-M/EM logs directory for entries showing users accessing reports outside their expected scope. Look for patterns where report IDs do not align with the user's typical access patterns.Affected if Audit logs show users successfully accessing or modifying reports they should not have permission to view or edit.
You are affected if your Control-M version is 9.0.20.x (before 238) or 9.0.21.x (before 201) AND the report management module is accessible to users who should have limited report access.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.0.20.2389.0.21.201
Apply vendor-supplied patches: upgrade to version 9.0.20.238 for branch 9.0.20 or version 9.0.21.201 for branch 9.0.21 to remediate the authorization bypass.
Upgrade to BMC Control-M version 9.0.20.238 or 9.0.21.201
- Identify the currently installed BMC Control-M version using the Control-M/EM version information or ctmemd -version command
- If running version 9.0.20.x where x < 238, plan to upgrade to version 9.0.20.238
- If running version 9.0.21.x where x < 201, plan to upgrade to version 9.0.21.201
- Review BMC Control-M upgrade documentation for the target version
- Back up the Control-M database and configuration before performing the upgrade
- Download the appropriate Control-M installation package from BMC Support (https://bmcservices.bmc.com)
- Execute the upgrade following BMC's standard upgrade procedure for your specific platform
- After upgrade, verify the new version using ctmemd -version or the Control-M/EM version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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