Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix insecure password storage in AsyncStorage#119

Open
TargetMisser wants to merge 1 commit intomainfrom
sentinel-fix-password-storage-18270886959965303458
Open

πŸ›‘οΈ Sentinel: [HIGH] Fix insecure password storage in AsyncStorage#119
TargetMisser wants to merge 1 commit intomainfrom
sentinel-fix-password-storage-18270886959965303458

Conversation

@TargetMisser
Copy link
Copy Markdown
Owner

🚨 Severity: HIGH
πŸ’‘ Vulnerability: User passwords were saved in plain text in AsyncStorage, an unencrypted storage mechanism. This occurred as a naive workaround because SecureStore has a 2048-byte limit on Android, failing to store large JSON arrays of passwords.
🎯 Impact: Anyone with physical access to an unlocked device or another app with sufficient permissions could extract plain text passwords.
πŸ”§ Fix: Implemented a hybrid storage pattern: lists of metadata are stored in AsyncStorage with secrets masked (e.g., password: '***'), and the actual secrets are stored individually in SecureStore using row-specific dynamic keys (e.g., aerostaff_pwd_${id}). Legacy plain text data is automatically migrated on mount.
βœ… Verification: Ensure tests pass (npm run typecheck and npx jest --passWithNoTests).


PR created automatically by Jules for task 18270886959965303458 started by @TargetMisser

Migrated password storage to use SecureStore for sensitive fields while keeping metadata in AsyncStorage to bypass Android size limits. Existing plain text passwords are automatically migrated.

Co-authored-by: TargetMisser <52361977+TargetMisser@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
flight-work-app Ready Ready Preview, Comment, Open in v0 Apr 22, 2026 1:18am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant