- Affected
- The Android build of the demo app
- What we found
- After sign-in, the app saves the user’s session token in a plain settings file instead of the platform’s secure storage, and the backend keeps accepting it for 30 days.
- Evidence
- A file listing and a redacted copy of the stored token, plus a request log showing the backend API accepting the copied token.
- Business impact
- A lost phone or a careless backup could hand someone access to the account without a password.
- How to fix it
- Store tokens in the platform’s secure storage instead of app settings.
- Shorten the token lifetime and revoke tokens on sign-out and password change.
- Exclude files with sensitive data from device backups.
- Retest
- After the fix, the token sits in secure storage and no longer appears in app files or backups. Closed.