Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to tamper with the vault configuration file leading to a man-in-the-middle vulnerability in Hub key loading mechanism. Before this fix, the client trusted endpoints from the vault config without host authenticity checks, which could allow token exfiltration by mixing a legitimate auth endpoint with a malicious API endpoint.
Impacted are users unlocking Hub-backed vaults with affected client versions in environments where an attacker can alter the vault.cryptomator file. This issue has been patched in version 1.19.1.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Cryptomator Cryptomator
cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
|
— |
1.19.1
|
References 4
https://github.com/cryptomator/cryptomator/commit/6b82abcd80449a30b561d823193f9…
security-advisories@github.com
https://github.com/cryptomator/cryptomator/pull/4179
security-advisories@github.com
https://github.com/cryptomator/cryptomator/releases/tag/1.19.1
security-advisories@github.com
https://github.com/cryptomator/cryptomator/security/advisories/GHSA-34rf-rwr3-7…
security-advisories@github.com