3 ms·
"Android app saves OAuth token in cleartext" Sheesh.
by leephillips 10y ago
"Android app saves OAuth token in cleartext"
Sheesh.
- mtgx 10y agoI think it's happening a lot more than you'd expect: http://www.bleepingcomputer.com/news/security/over-one-billion-android-users-susceptible-to-app-hijacking-via-oauth-2-0-attack/ http://www.bleepingcomputer.com/news/security/over-one-billi... Self-driving cars are going to be so much "fun" - for hackers.
- janvidar 10y agoYou are right, if the security sandbox is broken, then you have lost control. But at the same time, you also know that only 0.3% of the Android user base is using this year's version, and less than 25% are using last year's version. The security design of the app should reflect this.
- scarybeast 10y agoI'm not sure that "sheesh" is an appropriate response. It's perfectly valid for an app to reply on the security of its own storage space, and isolation from other apps, and drive encryption services of the platform. These are the guarantees provided by the underlying OS, and if they are broken, all bets are off. And what would you do differently? Any effort you put in here is going to cost you complexity and only likely provide security through obscurity. Fundamentally, the app has the authority to unlock and start the car. And a root exploit fundamentally has power over the app. This doesn't change even if you put the "key" material into hardware storage. Or maybe you could add an in-app password to encrypt the Tesla password? This is nasty UX, and the root exploit can still wait around for a moment when the password is provided. If there's any take away here, it is regarding Android. If you want a secure Android phone, choose it carefully. Very few Android phones keep up with the Google automatic security patch schedule. You may want one that does, such as a Pixel.
- leephillips 10y agoThat's a reasonable reply. I think my comment was hasty, made after skimming the article and not thinking about it too deeply.
- sowbug 10y agoYeah, they should encrypt the token. They should encrypt the encryption key as well. But the key to decrypt the encryption key is OK to store in plaintext, because by that point attackers will have lost interest.
- ranman 10y agoOut of curiosity doesn't this just mean the user access token and user access secret are in plaintext? Aren't those useless without the app token/secret -- so if the app is encrypted and you can't run strings to get those your only vector of attack is still through the app itself right? I'm not a security expert.