{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1371 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1371 is a medium-severity vulnerability in Ibm Websphere Mq, published on 17 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1371 and fix it if it is affected.\n\nWhat it is: CVE-2018-1371 is a medium-severity vulnerability in Ibm Websphere Mq, published on 17 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1371 in the wild and no public exploit code.\n\nAffected product: Ibm Websphere 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-2018-1371/ (Markdown: https://insights.sbomify.com/CVE-2018-1371/index.md)","id":"CVE-2018-1371","markdown":"https://insights.sbomify.com/CVE-2018-1371/index.md","name":"CVE-2018-1371","record":{"aliases":["GHSA-854x-j9wg-w8jp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM WebSphere MQ","requires_auth":"low_privilege","summary":"A client connection can trigger a segmentation fault in the channel process, causing a denial of service for IBM WebSphere MQ administrators.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"websphere_mq","vendor":"ibm"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"An IBM WebSphere MQ 8.0.0.8, 9.0.0.2, and 9.0.4 Client connecting to a MQ Queue Manager can cause a SIGSEGV in the AMQRMPPA channel process terminating it. IBM X-Force ID: 137771.","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":"Null dereference in MQ","id":"CVE-2018-1371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:websphere_mq","products":["ibm:websphere_mq"],"type":"null_dereference","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in Security Guardium Big Data Intelligence","id":"CVE-2018-1372"},"packages":[],"prev":{"headline":"Missing authorization in Security Guardium Big Data Intelligence","id":"CVE-2018-1370"},"products":["MQ"],"published":"2018-04-17","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-0896","kev_date_added":null,"published":"2009-06-03"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-6044","kev_date_added":null,"published":"2007-11-20"},{"cvss_score":8.8,"headline":"Command injection in MQ","id":"CVE-2018-1998","kev_date_added":null,"published":"2019-03-11"},{"cvss_score":8.8,"headline":"Code injection in MQ","id":"CVE-2018-1792","kev_date_added":null,"published":"2018-11-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2009-3160","kev_date_added":null,"published":"2009-09-10"},{"cvss_score":8.6,"headline":"Denial of service in WebSphere MQ","id":"CVE-2017-1145","kev_date_added":null,"published":"2017-03-20"},{"cvss_score":8.1,"headline":"Information disclosure in MQ","id":"CVE-2017-1337","kev_date_added":null,"published":"2017-07-10"}],"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-16","vendors":["IBM"]},"summary":"A client connection can trigger a segmentation fault in the channel process, causing a denial of service for IBM WebSphere MQ administrators.","url":"https://insights.sbomify.com/CVE-2018-1371/"}