{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4049 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4049 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4049 is a medium-severity denial of service vulnerability in Ibm Mq, published on 20 Aug 2019. 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-2019-4049 and fix it if it is affected.\n\nWhat it is: CVE-2019-4049 is a medium-severity denial of service vulnerability in Ibm Mq, published on 20 Aug 2019. 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-2019-4049 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-4049/ (Markdown: https://insights.sbomify.com/CVE-2019-4049/index.md)","id":"CVE-2019-4049","markdown":"https://insights.sbomify.com/CVE-2019-4049/index.md","name":"CVE-2019-4049","record":{"aliases":["GHSA-xhm5-vcjw-g9vf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM MQ","requires_auth":"none","summary":"A local user can cause a denial of service in IBM MQ by filling up the underlying filesystem via the error logging service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq","vendor":"ibm"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.0/PR:N/I:N/UI:N/AV:L/S:U/AC:L/A:H/C:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"IBM MQ 9.1.0.0, 9.1.0.1, 9.1.1, and 9.1.0.2 is vulnerable to a denial of service due to a local user being able to fill up the disk space of the underlying filesystem using the error logging service. IBM X-Force ID: 156398.","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-4049","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 API Connect","id":"CVE-2019-4051"},"packages":[],"prev":{"headline":"Information disclosure in Maximo Asset Management","id":"CVE-2019-4048"},"products":["MQ"],"published":"2019-08-20","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":"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-09-17","vendors":["IBM"]},"summary":"A local user can cause a denial of service in IBM MQ by filling up the underlying filesystem via the error logging service.","url":"https://insights.sbomify.com/CVE-2019-4049/"}