CVE-2018-17403
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe PhonePe wallet (aka com.PhonePe.app) application 3.0.6 through 3.3.26 for Android might allow attackers to impersonate a user and set up their account without their knowledge. 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe PhonePe wallet Android app versions 3.0.6-3.3.26 contains an accessibility services abuse vulnerability allowing a malicious app with accessibility permissions to impersonate users and set up accounts without authorization. Attackers can exploit the accessibility permission to capture user input, bypass authentication, or manipulate the app's UI flows to gain unauthorized access to wallet functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.6, <= 3.3.26CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PhonePe app installationCheck if the PhonePe wallet app is installed on the Android device. This can be done through Settings > Apps > App List, or by running: adb shell pm list packages | grep phonepeAffected if PhonePe wallet app is present on the device
-
Determine installed PhonePe versionLocate the installed version number in the app's settings (Settings > Apps > PhonePe > App info > Version) or via adb: adb shell dumpsys package com.phonepe.app | grep versionNameAffected if A version number is returned from the package manager
-
Compare version against affected rangeCompare the installed version number to the affected range 3.0.6 through 3.3.26. Versions 3.0.6, 3.0.7, 3.1.0, up to and including 3.3.26 are all affected.Affected if The installed version falls within >= 3.0.6 and <= 3.3.26
A user is affected if PhonePe wallet app version 3.0.6 through 3.3.26 is installed on their Android device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUsers should refrain from installing untrusted applications and should never grant accessibility permissions to unknown apps. The vendor should implement runtime detection of accessibility services and add additional authentication safeguards that cannot be bypassed through accessibility service manipulation.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17403 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17403 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data