{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4265 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4265 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4265 is a low-severity vulnerability in IBM Maximo Anywhere, published on 10 Oct 2019. 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-4265 and fix it if it is affected.\n\nWhat it is: CVE-2019-4265 is a low-severity vulnerability in IBM Maximo Anywhere, published on 10 Oct 2019. 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-4265 in the wild and no public exploit code.\n\nAffected product: IBM Maximo Anywhere. 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-4265/ (Markdown: https://insights.sbomify.com/CVE-2019-4265/index.md)","id":"CVE-2019-4265","markdown":"https://insights.sbomify.com/CVE-2019-4265/index.md","name":"CVE-2019-4265","record":{"aliases":["GHSA-vwj4-gmcv-4hc7"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Maximo Anywhere","requires_auth":"none","summary":"Attackers can gain sensitive device information due to missing root detection in IBM Maximo Anywhere mobile application.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_anywhere","vendor":"ibm"}],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:3.0/PR:N/I:N/C:L/AV:P/S:U/UI:N/A:N/AC:L/RL:O/RC:C/E:U","version":"3.0"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"IBM Maximo Anywhere 7.6.0, 7.6.1, 7.6.2, and 7.6.3 does not have device root detection which could result in an attacker gaining sensitive information about the device. IBM X-Force ID: 160198.","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 Maximo Anywhere","id":"CVE-2019-4265","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":"Security feature bypass in Maximo Anywhere","id":"CVE-2019-4266"},"packages":[],"prev":{"headline":"Security feature bypass in QRadar SIEM","id":"CVE-2019-4264"},"products":["Maximo Anywhere"],"published":"2019-10-10","related":[{"cvss_score":6.5,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4291","kev_date_added":null,"published":"2022-02-16"},{"cvss_score":5.4,"headline":"Cross-site scripting in Maximo Anywhere","id":"CVE-2017-1604","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":5,"headline":"Security feature bypass in n/a","id":"CVE-2015-4945","kev_date_added":null,"published":"2015-07-26"},{"cvss_score":4.3,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4286","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":4.3,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4288","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":3.5,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4349","kev_date_added":null,"published":"2020-11-03"},{"cvss_score":2.4,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4352","kev_date_added":null,"published":"2022-02-16"}],"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":"Attackers can gain sensitive device information due to missing root detection in IBM Maximo Anywhere mobile application.","url":"https://insights.sbomify.com/CVE-2019-4265/"}