{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55117 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55117 is a medium-severity memory corruption vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55117 and fix it if it is affected.\n\nWhat it is: CVE-2025-55117 is a medium-severity memory corruption vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-55117 in the wild and no public exploit code.\n\nAffected product: BMC Control-M/Agent. 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-55117/ (Markdown: https://insights.sbomify.com/CVE-2025-55117/index.md)","id":"CVE-2025-55117","markdown":"https://insights.sbomify.com/CVE-2025-55117/index.md","name":"CVE-2025-55117","record":{"aliases":["GHSA-2227-jcpx-8w3r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"BMC Control-M Agent","requires_auth":"none","summary":"Remote attackers can trigger a stack-based buffer overflow in BMC Control-M/Agent during SSL/TLS communication, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"airbus","cpe":[{"product":"control-m\\/agent","vendor":"bmc"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow can be remotely triggered when formatting an error message in the Control-M/Agent when SSL/TLS communication is configured.\n\nThe issue occurs in the following cases:\n\n  *  Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting \"use_openssl=n\";\n  *  Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings \"JAVA_AR=N\" and \"use_openssl=n\".","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/Agent buffer overflow in SSL/TLS communication","id":"CVE-2025-55117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"BMC Control-M/Agent memory corruption in SSL/TLS communication","id":"CVE-2025-55118"},"packages":[],"prev":{"headline":"BMC Control-M/Agent buffer overflow local privilege escalation","id":"CVE-2025-55116"},"products":["Control-M/Agent"],"published":"2025-09-16","related":[{"cvss_score":9.5,"headline":"BMC Control-M/Agent default SSL/TLS configuration authenticated bypass","id":"CVE-2025-55109","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":9.5,"headline":"BMC Control-M/Agent unescaped NULL byte in access control list checks","id":"CVE-2025-55113","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":9.3,"headline":"BMC Control-M/Agent path traversal local privilege escalation","id":"CVE-2025-55115","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":9.3,"headline":"BMC Control-M/Agent buffer overflow local privilege escalation","id":"CVE-2025-55116","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":7.6,"headline":"BMC Control-M/Agent hardcoded Blowfish keys","id":"CVE-2025-55112","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":5.7,"headline":"BMC Control-M/Agent insecure default file permissions","id":"CVE-2025-55111","kev_date_added":null,"published":"2025-09-16"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-16","vendors":["BMC"]},"summary":"Remote attackers can trigger a stack-based buffer overflow in BMC Control-M/Agent during SSL/TLS communication, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-55117/"}