{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48709 is a medium-severity vulnerability in BMC Control-M/Server, published on 7 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48709 and fix it if it is affected.\n\nWhat it is: CVE-2025-48709 is a medium-severity vulnerability in BMC Control-M/Server, published on 7 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48709 in the wild and no public exploit code.\n\nAffected product: BMC Control-M/Server. 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-2025-48709/ (Markdown: https://insights.sbomify.com/CVE-2025-48709/index.md)","id":"CVE-2025-48709","markdown":"https://insights.sbomify.com/CVE-2025-48709/index.md","name":"CVE-2025-48709","record":{"aliases":["GHSA-cgj5-r57f-xw42"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BMC Control-M Server","requires_auth":"low_privilege","summary":"An authenticated attacker with shell access can view cleartext database credentials in process lists and logs, allowing unauthorized database access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"control-m\\/server","vendor":"bmc"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-214","name":"Invocation of Process Using Visible Sensitive Information"}],"description":"BMC Control-M/Server 9.0.21.300 displays cleartext database credentials in process lists and logs. An authenticated attacker with shell access could observe these credentials and use them to log in to the database server. For example, when Control-M/Server on Windows has a database connection on, it runs 'DBUStatus.exe' frequently, which then calls 'dbu_connection_details.vbs' with the username, password, database hostname, and port written in cleartext, which can be seen in event and process logs in two separate locations. Fixed in PACTV.9.0.21.307.","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":"BMC Control-M/Server cleartext database credentials in process lists and logs","id":"CVE-2025-48709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"kro Confused Deputy vulnerability","id":"CVE-2025-48710"},"packages":[],"prev":{"headline":"Information disclosure in Ghostscript","id":"CVE-2025-48708"},"products":["Control-M/Server"],"published":"2025-08-07","related":[],"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-12-01","vendors":["BMC"]},"summary":"An authenticated attacker with shell access can view cleartext database credentials in process lists and logs, allowing unauthorized database access.","url":"https://insights.sbomify.com/CVE-2025-48709/"}