zzz

Incorrect Access Control in the Fingerprint Authentication Mechanism of "SMS text messaging app" App

Product introduction

Simple and fast SMS application that you can use to send SMS to your friends, family and people you know.Features:Night mode option, Color customization option, Block unwanted spam SMS, Organize all your messages in folders, Support for emoticons, Appointment for sending messages, Group messages, Delayed sending, Support dual SIM cards, Message search option, Customize fonts, Change text size, Fixed messages, Backup and restore all your messages.

Affected version

0.99.207

Vulnerability description

The following vulnerabilities exist in the implementation of the fingerprint authentication function of this app.

  1. The cryptographic parameter in fingerprint authentication is not configured securely and correctly, resulting in fingerprint authentication that can be bypassed.
  2. This app uses a deprecated version of the API (FingerprintManager) to implement the fingerprint authentication function, which makes the fingerprint function susceptible to UI attacks.
  3. Failure to disable the fingerprint function when a new fingerprint is added to the device, allowing an attacker to pass fingerprint authentication by entering a new fingerprint, which can lead to unauthorized access.
  4. Failure to verify the user’s identity when disabling the fingerprint feature, allowing the integrity of the fingerprint protection to be compromised, which can cause fingerprint protection to fail.

Vulnerability recurrence (For the first item in the vulnerability description)

  1. Enable fingerprint unlock feature for the “SMS text messaging app” app.
  2. Run frida-server on Android device.
  3. Inject the “fingerprint-bypass.js” script using Frida, hook the fingerprint authentication function “authenticate”, and spoof the authentication result. (Partial core code as shown below)
  4. Switch to the fingerprint unlock interface of “SMS text messaging app”, and find that you can unlock without fingerprint authentication.

Improvement suggestion

  1. When using the fingerprint authentication API “authenticate”, safely set its cryptographic parameter to a pre-created key, and verify the validity of the key after users have verified their fingerprints, so as to ensure that the user is truly authenticated. (refer to ***https://developer.android.com/training/sign-in/biometric-auth*** )
  2. It is recommended to use the latest version of the fingerprint API (BiometricPrompt) for stronger security and protection. However, this API suffers from the problem of incompatibility with Android versions below 9. If you consider the compatibility issue, you can use the library “androidx.biometric” provided by Google.
  3. Disable fingerprint authentication when a new fingerprint is recognized on the device, prompt the user when he/she performs fingerprint authentication, and require the user to complete the authentication by other means. In terms of implementation, this can be done by using the “setInvalidatedByBiometricEnrollment” API of the key used in fingerprint authentication.
  4. Verify the user’s identity when turning off the fingerprint function, and allow the user to turn off the fingerprint function only if the verification is passed.