rotki before 1.44.2 Weak Key Derivation for Premium Cloud Backup Encryption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.44.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Rotki, a privacy-focused portfolio tracking application, is affected by a flaw in how it derives the encryption key for premium cloud backups. An attacker who obtains an uploaded backup could guess the user's password offline and then decrypt the data, exposing exchange API keys, secrets, wallet addresses, and transaction history.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
rotki before 1.44.2 contains a weak key derivation vulnerability that allows attackers to brute-force backups because the premium sync key is a single unsalted SHA-256 of the user password. Attackers who obtain an uploaded backup blob can run GPU-parallel offline password guessing and decrypt the database containing exchange API keys, secrets, wallet addresses and transaction history.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- rotki rotki
fixed in 1.44.2