Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCryptomator
APPCryptomator< 1.19.1
Related vulnerabilities
Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vu...
Cryptomator for IOS offers multi-platform transparent client-side encryption for files in the cloud. Prior to ...
Cryptomator for Android offers multi-platform transparent client-side encryption for files in the cloud. Prior...
Cryptomator is data encryption software for users who store their files in the cloud. Prior to version 1.9.2, ...
Cryptomator through 1.6.5 allows DYLIB injection because, although it has the flag 0x1000 for Hardened Runtime...