Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Issue: App remains unlocked after failed biometric authentication and backgrounding #11667

Open
bigchu opened this issue Jan 17, 2025 · 1 comment
Labels
bug It's a bug

Comments

@bigchu
Copy link

bigchu commented Jan 17, 2025

Operating system

Android

Joplin version

Joplin Mobile 3.2.7 (prod, android)

Desktop version info

Joplin Mobile 3.2.7 (prod, android)

Client ID: 6d2427a3c141471290718f5ab6a352e3

Sync Version: 3
Profile Version: 47
Keychain Supported: No

Revision: 2fba101 (dev)

Android API level: 34
WebView version: 131.0.6778.260
WebView package: com.google.android.webview
FTS enabled: 1
Hermes enabled: 1

Current behaviour

Description:
A security issue occurs in the Joplin Android app (version 3.2.7 and earlier) where the app remains in an unlocked state under specific conditions. Below are the steps to reproduce the issue:


Steps to Reproduce:

  1. Attempt to unlock the app using biometric authentication, but fail or cancel the authentication.
  2. Press the OS back button twice to send the app to the background.
  3. Reopen the app from the background.

Expected Behavior:
The app should require biometric authentication again upon returning from the background.

Actual Behavior:
The app remains in an unlocked state, bypassing the intended security feature.


Let me know if further details or logs are required. Thank you for looking into this!


Expected behaviour

No response

Logs

No response

@bigchu bigchu added the bug It's a bug label Jan 17, 2025
@laurent22
Copy link
Owner

laurent22 commented Jan 17, 2025

This is a known issue unfortunately and the reason it's a beta feature on Android. It works perfectly well on some devices and is faulty on others, and so far we are not able to replicate the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug
Projects
None yet
Development

No branches or pull requests

2 participants