{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-4945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-4945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-4945 is a medium-severity vulnerability in n/a, published on 26 Jul 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2015-4945 and fix it if it is affected.\n\nWhat it is: CVE-2015-4945 is a medium-severity vulnerability in n/a, published on 26 Jul 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2015-4945 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2015-4945/ (Markdown: https://insights.sbomify.com/CVE-2015-4945/index.md)","id":"CVE-2015-4945","markdown":"https://insights.sbomify.com/CVE-2015-4945/index.md","name":"CVE-2015-4945","record":{"aliases":["GHSA-qmc3-jwrp-rgjm"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Maximo Anywhere","requires_auth":"none","summary":"Attackers can bypass passcode protection in IBM Maximo Anywhere for Android via a crafted application to obtain sensitive information.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_anywhere","vendor":"ibm"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Unspecified vulnerability in the IBM Maximo Anywhere application 7.5.1 through 7.5.1.2 for Android allows attackers to bypass a passcode protection mechanism and obtain sensitive information via a crafted application.","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":"Security feature bypass in n/a","id":"CVE-2015-4945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2015-4946"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-4944"},"products":["n/a"],"published":"2015-07-26","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":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-08-06","vendors":["n/a"]},"summary":"Attackers can bypass passcode protection in IBM Maximo Anywhere for Android via a crafted application to obtain sensitive information.","url":"https://insights.sbomify.com/CVE-2015-4945/"}