{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4731 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4731 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4731 is a medium-severity vulnerability in IBM MQ Appliance, published on 28 Jul 2020. 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-4731 and fix it if it is affected.\n\nWhat it is: CVE-2019-4731 is a medium-severity vulnerability in IBM MQ Appliance, published on 28 Jul 2020. 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-4731 in the wild and no public exploit code.\n\nAffected product: IBM MQ Appliance. 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-4731/ (Markdown: https://insights.sbomify.com/CVE-2019-4731/index.md)","id":"CVE-2019-4731","markdown":"https://insights.sbomify.com/CVE-2019-4731/index.md","name":"CVE-2019-4731","record":{"aliases":["GHSA-43gf-9mf8-44g5"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM MQ Appliance","requires_auth":"none","summary":"A local attacker can obtain highly sensitive information from trace logs in the IBM MQ Appliance.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq_appliance","vendor":"ibm"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/A:N/C:H/AC:H/S:U/PR:N/I:N/UI:N/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM MQ Appliance 9.1.4.CD could allow a local attacker to obtain highly sensitive information by inclusion of sensitive data within trace. IBM X-Force ID: 172616.","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":"Information disclosure in MQ Appliance","id":"CVE-2019-4731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Other in Java","id":"CVE-2019-4732"},"packages":[],"prev":{"headline":"XML external entity in Cognos Analytics","id":"CVE-2019-4730"},"products":["MQ Appliance"],"published":"2020-07-28","related":[{"cvss_score":8.8,"headline":"IBM MQ code execution","id":"CVE-2025-0975","kev_date_added":null,"published":"2025-02-28"},{"cvss_score":8.8,"headline":"Command injection in MQ Appliance","id":"CVE-2017-1318","kev_date_added":null,"published":"2017-07-18"},{"cvss_score":8.4,"headline":"Security feature bypass in MQ Appliance","id":"CVE-2019-4620","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":8.2,"headline":"Code injection in MQ Appliance","id":"CVE-2021-38967","kev_date_added":null,"published":"2021-11-30"},{"cvss_score":7.5,"headline":"IBM MQ code execution","id":"CVE-2024-25048","kev_date_added":null,"published":"2024-04-27"},{"cvss_score":6.7,"headline":"IBM MQ privilege escalation","id":"CVE-2023-46176","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":6.5,"headline":"IBM MQ denial of service","id":"CVE-2025-3631","kev_date_added":null,"published":"2025-07-11"}],"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 attacker can obtain highly sensitive information from trace logs in the IBM MQ Appliance.","url":"https://insights.sbomify.com/CVE-2019-4731/"}