{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22489 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22489 is a high-severity vulnerability in Ibm Mq, published on 19 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22489 and fix it if it is affected.\n\nWhat it is: CVE-2022-22489 is a high-severity vulnerability in Ibm Mq, published on 19 Aug 2022. 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-2022-22489 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-2022-22489/ (Markdown: https://insights.sbomify.com/CVE-2022-22489/index.md)","id":"CVE-2022-22489","markdown":"https://insights.sbomify.com/CVE-2022-22489/index.md","name":"CVE-2022-22489","record":{"aliases":["GHSA-4f9w-3c78-j5r7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM MQ","requires_auth":"none","summary":"Remote attackers can exploit XML External Entity injection in IBM MQ to expose sensitive information or cause memory exhaustion.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq","vendor":"ibm"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/S:U/A:L/PR:N/UI:N/AC:L/C:H/I:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"IBM MQ 8.0, (9.0, 9.1, 9.2 LTS), and (9.1 and 9.2 CD) are vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 226339.","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":"XML external entity in MQ","id":"CVE-2022-22489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:mq","products":["ibm:mq"],"type":"xxe","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Robotic Process Automation","id":"CVE-2022-22490"},"packages":[],"prev":{"headline":"IBM OpenBMC denial of service","id":"CVE-2022-22488"},"products":["MQ"],"published":"2022-08-19","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.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-16","vendors":["IBM"]},"summary":"Remote attackers can exploit XML External Entity injection in IBM MQ to expose sensitive information or cause memory exhaustion.","url":"https://insights.sbomify.com/CVE-2022-22489/"}