Skip to content

MASWE-0046: Crypto Keys Not Invalidated on New Biometric Enrollment

Content in BETA

This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).

Send Feedback

Draft Weakness

This weakness hasn't been created yet and it's in draft. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.

Check our GitHub Issues for MASWE-0046

Initial Description or Hints

Biometric related crypto keys should be is invalidated by default whenever new biometric enrollments are added.

Relevant Topics

  • Enabled by default on Android but can be disabled by calling setInvalidatedByBiometricEnrollment(false)
  • Disabled by default on iOS but can be enabled using SecAccessControlCreateFlags.biometryCurrentSet (prev. touchIDCurrentSet) when setting access control (since iOS 9). This invalidates keychain items when a fingerprint is added or removed. See kSecAccessControlTouchIDCurrentSet, biometryCurrentSet.

MASTG v1 Coverage

No MASTG v1 tests are related to this weakness.