CVE-2024-1605
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 · uneditedBMC 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.
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 confidenceBMC Control-M versions 9.0.20 and 9.0.21 load Dynamic Link Libraries (DLLs) from a directory with world-writable permissions. An attacker with write access to this directory can place a malicious DLL that will be automatically loaded and executed with the application's privileges upon user login, achieving local privilege escalation.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Control-M versionUse the Control-M utilities or check version files in the Control-M installation directory (typically under /opt/controlm or C:\ControlM) to determine the exact version numberAffected if The installed version is 9.0.20 (any patch below 238) or 9.0.21 (any patch below 201)
-
Locate the Control-M DLL loading directoryExamine Control-M configuration files or process behavior to identify directories from which the application loads dynamic libraries at runtimeAffected if A DLL loading directory exists within the Control-M installation or runtime path
-
Check directory permissions for world-writable accessUse OS commands (such as 'ls -ld' on Unix or 'icacls' on Windows) to inspect the permissions on the identified DLL loading directoryAffected if The directory shows world-writable or equivalent permissions (Everyone:Write, 777, or similar)
-
Verify if unprivileged users can write to the DLL directoryAttempt to create a test file in the identified directory using a non-admin account, or review ACLs to confirm write access for non-privileged usersAffected if Non-administrative or unprivileged users have write permissions to the directory
You are affected if Control-M version is 9.0.20.x before 9.0.20.238 or 9.0.21.x before 9.0.21.201 AND a DLL loading directory used by Control-M has world-writable permissions that allow unprivileged users to place files.
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 the vendor patches: upgrade Control-M 9.0.20 to version 9.0.20.238 or 9.0.21 to version 9.0.21.201. As an interim mitigation, restrict file system permissions on the DLL loading directory to prevent unauthorized write access.
9.0.20.238 or 9.0.21.201 (depending on current branch)
- Identify current Control-M version by checking the installed version in the Control-M environment or using the version check utility
- If running 9.0.20.x (where x < 238), plan upgrade to version 9.0.20.238
- If running 9.0.21.x (where x < 201), plan upgrade to version 9.0.21.201
- Review BMC Control-M upgrade documentation for the target version
- Execute upgrade in a test environment first to validate
- Apply upgrade to production environment following standard change management procedures
- Verify the new version is running post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1605 — 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-1605 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