{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-4614 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4614 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4614 is a medium-severity denial of service vulnerability in Ibm Mq, published on 28 Jan 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-4614 and fix it if it is affected.\n\nWhat it is: CVE-2019-4614 is a medium-severity denial of service vulnerability in Ibm Mq, published on 28 Jan 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-4614 in the wild and no public exploit code.\n\nAffected product: Ibm Mq. 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-4614/ (Markdown: https://insights.sbomify.com/CVE-2019-4614/index.md)","id":"CVE-2019-4614","markdown":"https://insights.sbomify.com/CVE-2019-4614/index.md","name":"CVE-2019-4614","record":{"aliases":["GHSA-ff94-3j58-q72h"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM MQ","requires_auth":"low_privilege","summary":"A client connecting to IBM MQ Queue Manager can cause a denial of service via SIGSEGV when processing an invalid message.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq","vendor":"ibm"},{"product":"mq_appliance","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/C:N/AC:H/I:N/PR:L/UI:N/S:U/A:H/RC:C/E:U/RL:O","version":"3.0"},"cwes":[],"description":"IBM MQ and IBM MQ Appliance 8.0 and 9.0 LTS client connecting to a Queue Manager could cause a SIGSEGV denial of service caused by converting an invalid message. IBM X-Force ID: 168639.","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":"Denial of service in MQ","id":"CVE-2019-4614","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:mq","products":["ibm:mq"],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Cloud Automation Manager","id":"CVE-2019-4616"},"packages":[],"prev":{"headline":"Cross-site request forgery in Planning Analytics","id":"CVE-2019-4613"},"products":["MQ"],"published":"2020-01-28","related":[{"cvss_score":8.8,"headline":"IBM MQ queue manager is vulnerable to remote code execution","id":"CVE-2026-10575","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.8,"headline":"IBM MQ queue manager is vulnerable to remote code execution","id":"CVE-2026-11375","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.8,"headline":"IBM MQ queue manager is vulnerable to remote code execution","id":"CVE-2026-11378","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.2,"headline":"XML external entity in MQ","id":"CVE-2022-22489","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":8.1,"headline":"IBM MQ queue manager is vulnerable to unauthenticated remote code execution","id":"CVE-2026-10027","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.1,"headline":"Deserialization in MQ","id":"CVE-2020-4682","kev_date_added":null,"published":"2021-01-28"},{"cvss_score":7.5,"headline":"IBM MQ queue manager is vulnerable to remote code execution","id":"CVE-2026-10853","kev_date_added":null,"published":"2026-09-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["IBM"]},"summary":"A client connecting to IBM MQ Queue Manager can cause a denial of service via SIGSEGV when processing an invalid message.","url":"https://insights.sbomify.com/CVE-2019-4614/"}