{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17400 is a high-severity vulnerability in n/a, published on 23 Sep 2018. 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-2018-17400 and fix it if it is affected.\n\nWhat it is: CVE-2018-17400 is a high-severity vulnerability in n/a, published on 23 Sep 2018. 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-2018-17400 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-2018-17400/ (Markdown: https://insights.sbomify.com/CVE-2018-17400/index.md)","id":"CVE-2018-17400","markdown":"https://insights.sbomify.com/CVE-2018-17400/index.md","name":"CVE-2018-17400","record":{"aliases":["GHSA-pv8p-frrc-h2w3"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"PhonePe Android app","requires_auth":"none","summary":"Attackers can steal user credentials during initial setup by intercepting input via malicious apps with accessibility permissions, leading to account takeover.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phonepe","vendor":"phonepe"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"The PhonePe wallet (aka com.PhonePe.app) application 3.0.6 through 3.3.26 for Android might allow attackers to perform Account Takeover attacks by intercepting the user name and PIN during the initial configuration of the application.  NOTE: the vendor says that, to exploit this, the user has to explicitly install a malicious app and provide accessibility permission to the malicious app, that the Android platform provides fair warnings to the users before turning on accessibility for any application, and that it believes it is similar to installing malicious keyboards, or malicious apps taking screenshots","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 n/a","id":"CVE-2018-17400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2018-17401"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-17399"},"products":["n/a"],"published":"2018-09-23","related":[{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2018-17401","kev_date_added":null,"published":"2018-09-23"},{"cvss_score":8.8,"headline":"Business logic in n/a","id":"CVE-2018-17403","kev_date_added":null,"published":"2018-09-23"},{"cvss_score":5.8,"headline":"WordPress PhonePe Payment Solutions Plugin \u003c= 1.0.15 is vulnerable to Server Side Request Forgery (SSRF)","id":"CVE-2022-45835","kev_date_added":null,"published":"2023-11-13"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-17402","kev_date_added":null,"published":"2018-09-23"},{"cvss_score":4.6,"headline":"PhonePe App SQLite Database databases cleartext storage in file","id":"CVE-2025-5154","kev_date_added":null,"published":"2025-05-25"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers can steal user credentials during initial setup by intercepting input via malicious apps with accessibility permissions, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2018-17400/"}