{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-1605 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-1605 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1605 is a medium-severity vulnerability in BMC Control-M, published on 18 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-1605 and fix it if it is affected.\n\nWhat it is: CVE-2024-1605 is a medium-severity vulnerability in BMC Control-M, published on 18 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-1605 in the wild and no public exploit code.\n\nAffected product: BMC Control-M. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-1605/ (Markdown: https://insights.sbomify.com/CVE-2024-1605/index.md)","id":"CVE-2024-1605","markdown":"https://insights.sbomify.com/CVE-2024-1605/index.md","name":"CVE-2024-1605","record":{"aliases":["GHSA-wpc3-225m-fg2m"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Workload automation software","requires_auth":"none","summary":"Attackers can execute arbitrary code with application privileges by placing malicious DLLs in a world-writable directory loaded during user login.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"control-m","vendor":"bmc"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"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. \n\nFix 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"DLL side-loading in BMC Control-M","id":"CVE-2024-1605","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"HTML injection in BMC Control-M","id":"CVE-2024-1606"},"packages":[],"prev":{"headline":"Incorrect authorization in BMC Control-M","id":"CVE-2024-1604"},"products":["Control-M"],"published":"2024-03-18","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-39122","kev_date_added":null,"published":"2023-07-31"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-26550","kev_date_added":null,"published":"2023-02-25"},{"cvss_score":6.4,"headline":"Incorrect authorization in BMC Control-M","id":"CVE-2024-1604","kev_date_added":null,"published":"2024-03-18"},{"cvss_score":4.6,"headline":"HTML injection in BMC Control-M","id":"CVE-2024-1606","kev_date_added":null,"published":"2024-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["BMC"]},"summary":"Attackers can execute arbitrary code with application privileges by placing malicious DLLs in a world-writable directory loaded during user login.","url":"https://insights.sbomify.com/CVE-2024-1605/"}