Open Bug 1851670 Opened 9 months ago Updated 1 month ago

mozilla.components.service.sync.logins.LoginsCrypto Crash in [@ android.security.KeyStoreException: at android.security.KeyStore2.getKeyStoreException(KeyStore2.java)]

Categories

(Fenix :: Logins, defect, P3)

Unspecified
Android

Tracking

(firefox118 disabled, firefox119 disabled, firefox120 affected)

Tracking Status
firefox118 --- disabled
firefox119 --- disabled
firefox120 --- affected

People

(Reporter: cpeterson, Unassigned)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/27451fa2-341d-4c60-a170-9b3f40230905

Frame   Module  Function  Source  In app?
0   android.security.KeyStore2  getKeyStoreException  KeyStore2.java:356
1   android.security.KeyStoreSecurityLevel  createOperation   KeyStoreSecurityLevel.java:120
2   android.security.keystore2.AndroidKeyStoreCipherSpiBase   ensureKeystoreOperationInitialized  AndroidKeyStoreCipherSpiBase.java:334 
3   android.security.keystore2.AndroidKeyStoreCipherSpiBase   engineInit  AndroidKeyStoreCipherSpiBase.java:171 
4   javax.crypto.Cipher   tryTransformWithProvider  Cipher.java:2984
5   javax.crypto.Cipher   tryCombinations   Cipher.java:2891
6   javax.crypto.Cipher$SpiAndProviderUpdater   updateAndGetSpiAndProvider  Cipher.java:2796
7   javax.crypto.Cipher   chooseProvider  Cipher.java:773 
8   javax.crypto.Cipher   init  Cipher.java:1143
9   javax.crypto.Cipher   init  Cipher.java:1084
10  mozilla.components.lib.dataprotect.SecurePreferencesImpl23  putString   SecureAbove22Preferences.kt:87
11  mozilla.components.lib.dataprotect.SecureAbove22Preferences   putString   SecureAbove22Preferences.kt:8 
12  mozilla.components.service.sync.logins.LoginsCrypto   storeKeyAndCanary   LoginsCrypto.kt:10
13  mozilla.components.concept.storage.KeyManager   getManagedKey   KeyManager.kt:79
14  mozilla.components.concept.storage.KeyManager   getOrGenerateKey$suspendImpl  KeyManager.kt:94
15  mozilla.components.service.sync.logins.SyncableLoginsStorage$list$2   invokeSuspend   SyncableLoginsStorage.kt:36 
16  mozilla.components.service.sync.logins.SyncableLoginsStorage$list$2   invoke  SyncableLoginsStorage.kt:13 
17  kotlinx.coroutines.intrinsics.UndispatchedKt  startUndispatchedOrReturn   Undispatched.kt:5 
18  kotlinx.coroutines.BuildersKt   withContext   :76 
19  mozilla.components.service.sync.logins.SyncableLoginsStorage  list  SyncableLoginsStorage.kt:11 
20  org.mozilla.fenix.FenixApplication$setStartupMetrics$4  invokeSuspend   FenixApplication.kt:168 
21  kotlin.coroutines.jvm.internal.BaseContinuationImpl   resumeWith  ContinuationImpl.kt:9 
22  kotlinx.coroutines.DispatchedTask   run   DispatchedTask.kt:112 
23  kotlinx.coroutines.internal.LimitedDispatcher$Worker  run   LimitedDispatcher.kt:4
24  kotlinx.coroutines.scheduling.TaskImpl  run   Tasks.kt:3
25  kotlinx.coroutines.scheduling.CoroutineScheduler$Worker   run   CoroutineScheduler.kt:96

This crash [@ android.security.KeyStoreException: at android.security.KeyStore.getKeyStoreException(KeyStore.java) ] looks similar, so I'll add the signature here. Example: bp-0a7871a1-f426-442c-8d25-b4f310230914

Crash Signature: [@ android.security.KeyStoreException: at android.security.KeyStore2.getKeyStoreException(KeyStore2.java)] → [@ android.security.KeyStoreException: at android.security.KeyStore2.getKeyStoreException(KeyStore2.java)] [@ android.security.KeyStoreException: at android.security.KeyStore.getKeyStoreException(KeyStore.java) ]

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Keywords: topcrash

The severity field is not set for this bug.
:aputanu, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(aputanu)
Flags: sec-bounty?
Severity: -- → S2
Flags: needinfo?(aputanu)

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.

Keywords: topcrash

Since the crash volume is low (less than 15 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit BugBot documentation.

Severity: S2 → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.