{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19215 is a high-severity memory corruption vulnerability in n/a, published on 30 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19215 and fix it if it is affected.\n\nWhat it is: CVE-2019-19215 is a high-severity memory corruption vulnerability in n/a, published on 30 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19215 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-19215/ (Markdown: https://insights.sbomify.com/CVE-2019-19215/index.md)","id":"CVE-2019-19215","markdown":"https://insights.sbomify.com/CVE-2019-19215/index.md","name":"CVE-2019-19215","record":{"aliases":["GHSA-wfjr-fx5q-m6gw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"BMC Control-M Agent","requires_auth":"low_privilege","summary":"Remote attackers can exploit a buffer overflow in BMC Control-M Agent when email notifications are enabled, potentially leading to code execution or service disruption.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"control-m\\/agent","vendor":"bmcsoftware"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"A buffer overflow vulnerability in BMC Control-M/Agent 7.0.00.000 when the On-Do action destination is Mail and the Control-M/Agent is configured to send the email, allows remote attackers to have unspecified impact via vectors related to the configured IP address or SMTP server.","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":"Memory corruption in n/a","id":"CVE-2019-19215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19216"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-19214"},"products":["n/a"],"published":"2020-04-30","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-19216","kev_date_added":null,"published":"2020-04-30"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2019-19217","kev_date_added":null,"published":"2020-04-30"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2019-19220","kev_date_added":null,"published":"2020-04-30"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19218","kev_date_added":null,"published":"2020-04-30"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2019-19219","kev_date_added":null,"published":"2020-04-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can exploit a buffer overflow in BMC Control-M Agent when email notifications are enabled, potentially leading to code execution or service disruption.","url":"https://insights.sbomify.com/CVE-2019-19215/"}