{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-41734 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41734 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41734 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 17 Feb 2023. 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-41734 and fix it if it is affected.\n\nWhat it is: CVE-2022-41734 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 17 Feb 2023. 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-41734 in the wild and no public exploit code.\n\nAffected product: Ibm Maximo Asset Management. 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-41734/ (Markdown: https://insights.sbomify.com/CVE-2022-41734/index.md)","id":"CVE-2022-41734","markdown":"https://insights.sbomify.com/CVE-2022-41734/index.md","name":"CVE-2022-41734","record":{"aliases":["GHSA-mfq2-2phj-f7gw"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"none","summary":"Remote attackers can obtain sensitive information via detailed technical error messages in IBM Maximo Asset Management, aiding further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_application_suite","vendor":"ibm"},{"product":"maximo_asset_management","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Maximo Asset Management 7.6.1.2 and 7.6.1.3 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser.  This information could be used in further attacks against the system.  IBM X-Force ID:  237587.","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 Maximo Asset Management information disclosure","id":"CVE-2022-41734","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management"],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Business Process Manager cross-site scripting","id":"CVE-2022-41735"},"packages":[],"prev":{"headline":"IBM InfoSphere Information Server denial of service","id":"CVE-2022-41733"},"products":["Maximo Asset Management"],"published":"2023-02-17","related":[{"cvss_score":9.8,"headline":"There is a vulnerability in the IBM Maximo Manage application in IBM Maximo Application Suite for Cognos Analytics","id":"CVE-2025-36386","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":8.2,"headline":"IBM Maximo Application Suite XML external entity injection","id":"CVE-2024-27266","kev_date_added":null,"published":"2024-03-14"},{"cvss_score":7.5,"headline":"IBM Maximo Application Suite privilege escalation","id":"CVE-2025-2898","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":7.5,"headline":"IBM Maximo Application Suite information disclosure","id":"CVE-2024-22328","kev_date_added":null,"published":"2024-04-06"},{"cvss_score":6.5,"headline":"IBM Maximo Application Suite improper access control","id":"CVE-2023-43037","kev_date_added":null,"published":"2025-04-10"},{"cvss_score":6.4,"headline":"Maximo Asset Management cross-site scripting","id":"CVE-2023-38723","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":6.4,"headline":"IBM Maximo Asset Management cross-site scripting","id":"CVE-2022-35645","kev_date_added":null,"published":"2023-03-02"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-12","vendors":["IBM"]},"summary":"Remote attackers can obtain sensitive information via detailed technical error messages in IBM Maximo Asset Management, aiding further attacks.","url":"https://insights.sbomify.com/CVE-2022-41734/"}