Rotki
Monthly
rotki before 1.44.2 derives the encryption key for its premium cloud backup/sync feature as a single unsalted SHA-256 hash of the user password, so anyone who obtains an uploaded backup blob can run offline, GPU-parallel password guessing against it and decrypt the database it holds - exchange API keys, secrets, wallet addresses and transaction history. The attack is unauthenticated and requires no user interaction once the blob is in hand, and only users of the premium sync/backup feature are affected. There is no KEV entry and no public exploit identified at time of analysis, though the CVSS 4.0 score of 8.2 signals high confidentiality impact; the vendor addressed the issue in rotki 1.44.2.
rotki before 1.44.2 derives the encryption key for its premium cloud backup/sync feature as a single unsalted SHA-256 hash of the user password, so anyone who obtains an uploaded backup blob can run offline, GPU-parallel password guessing against it and decrypt the database it holds - exchange API keys, secrets, wallet addresses and transaction history. The attack is unauthenticated and requires no user interaction once the blob is in hand, and only users of the premium sync/backup feature are affected. There is no KEV entry and no public exploit identified at time of analysis, though the CVSS 4.0 score of 8.2 signals high confidentiality impact; the vendor addressed the issue in rotki 1.44.2.