{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-28950 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-28950 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-28950 is a medium-severity vulnerability in Ibm Mq, published on 19 May 2023. 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-2023-28950 and fix it if it is affected.\n\nWhat it is: CVE-2023-28950 is a medium-severity vulnerability in Ibm Mq, published on 19 May 2023. 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-2023-28950 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-2023-28950/ (Markdown: https://insights.sbomify.com/CVE-2023-28950/index.md)","id":"CVE-2023-28950","markdown":"https://insights.sbomify.com/CVE-2023-28950/index.md","name":"CVE-2023-28950","record":{"aliases":["GHSA-cp82-6cf7-h4f6"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"IBM MQ","requires_auth":"none","summary":"Attackers can read sensitive user information from trace files in IBM MQ if tracing is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq","vendor":"ibm"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"IBM MQ 8.0, 9.0, 9.1, 9.2, and 9.3 could disclose sensitive user information from a trace file if that functionality has been enabled.  IBM X-Force ID:  251358.","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":"IBM MQ information disclosure","id":"CVE-2023-28950","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:mq","products":["ibm:mq"],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Cognos Controller log injection","id":"CVE-2023-28952"},"packages":[],"prev":{"headline":"IBM Engineering Requirements Management cross-site request forgery","id":"CVE-2023-28949"},"products":["MQ"],"published":"2023-05-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.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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-12","vendors":["IBM"]},"summary":"Attackers can read sensitive user information from trace files in IBM MQ if tracing is enabled.","url":"https://insights.sbomify.com/CVE-2023-28950/"}