Evernote checks for update over unencrypted HTTP, and the update packages are also downloaded over HTTP. But it’s signed code, right? What could go wrong?
It’s trivially easy to perform a man-in-the-middle attack to prevent future updates from ever being received, or to redirect the user to unsigned or malicious code, that may or may not run.
There is a DSA signature on the file at the update URL, and there’s signatures on the files and a certificate OU deep within the app contents… but that all assumes the user can get to the update, and download it securely.
Good news for persistent threats, bad news for the millions of Evernote users who want to get critical security updates.
This looks easy enough to fix.
(Submitted by Phillip Knoll)
August 19th, 2014 8:38am
