Keepassdroid corrupts existing database on save

[lucebac]

Hey there, unfortunate situation happened on my phone tonight. I added a password to an existing KDBX file and after a save the database was corrupt and could not be opened anymore - even with Keepassdroid.

I was able to recreate the issue using the following steps (I also attached the files I created):

• create a new Keepass Database with KeepassXC
• in the encryption settings choose the following:
  • encryption algorithm: AES 256-bit
  • key derivation function: AES-KDF (KDBX 4)
  • transform rounds: 1'000'000
• continue, set any password, save database, and copy database to phone
• open with keepassdroid and create a new password
• close app to save
• try re-opening the database. it won't work.

I diffed the broken file with the original one and it seems that Keepassdroid set the file version down to 3.1 from the original 4.0 (broken database on the left, original on the right):

By skimming through the code I believe I narrowed down the issue to be happening in getMinKdbxVersion where the logic falls back to returning version 3.1.

Please find attached my test databases. The password I chose was test. databases.zip

If you need more details or can't reproduce the issue, please let me know and I'll happily provide more information. Thanks for your great work!

[Scaninky]

I am having the same problem.... Galaxy s21 latest android. My file stored on google drive. Will not open...... says Corrupted but when i go to my laptop it does open from there.