Live data from Hacker News

Hackers can pwn your Android in 10 seconds, if you use Bing App in Starbucks

blog.trustlook.com

31–34 of 34 posts

Re: Hackers can pwn your Android in 10 seconds, if you use Bing App in Starbucks

#31
post #20

Does this bug affect only android phones that are rooted? It flashes saying that the bing App got root permission. I think that's disabled unless the phone was jailbroken.

Correct. Even for the not rooted phones, attackers can send SMS, record audio or access SD card due to the permissions the target app applied. Also you may exploit some privilege escalation vulnerability on Android after you got a shell. It's phone-specific and app-specific though.

Re: Hackers can pwn your Android in 10 seconds, if you use Bing App in Starbucks

#32
post #18

Earlier quoted context omitted.

iOS apps cannot be targeted in this way because they don't have the JavaScript bridge.

Not exactly. iOS 7+ introduced Cocoa Javascript bridging capabilities in the public APIs. Before that, similar iOS APIs had existed as "private" ones (so, very uncommonly used outside of apple's own apps). iOS doesn't bridge Javascript to _Java_ which is why this particular attack wouldn't work. But the JS Cocoa stuff is still pretty young, so wait and see ;)

The JS-Cocoa bridge isn't young at all, it's the same bridge that has been on Mac OS X for years. And it's opt-in -- on the native side you have to specify which classes can be bridged and what methods can be called. It's not the case that any bridged webview exposes all of Cocoa for your JS injection pleasure. You could write an app that specifically exposed some dangerous API, but you'd know you had done so.

Re: Hackers can pwn your Android in 10 seconds, if you use Bing App in Starbucks

#33

Earlier quoted context omitted.

Not exactly. iOS 7+ introduced Cocoa Javascript bridging capabilities in the public APIs. Before that, similar iOS APIs had existed as "private" ones (so, very uncommonly used outside of apple's own apps). iOS doesn't bridge Javascript to _Java_ which is why this particular attack wouldn't work. But the JS Cocoa stuff is still pretty young, so wait and see ;)

The JS-Cocoa bridge isn't young at all, it's the same bridge that has been on Mac OS X for years. And it's opt-in -- on the native side you have to specify which classes can be bridged and what methods can be called. It's not the case that any bridged webview exposes all of Cocoa for your JS injection pleasure. You could write an app that specifically exposed some dangerous API, but you'd know you had done so.

> You could write an app that specifically exposed some dangerous API, but you'd know you had done so.

Few people write insecure code on purpose. Of course the same is true of Safari or networking/parsing code. I still maintain certificate pinning is the answer here, to try and defend as much as possible against MITM in the first place.

Post reply on HN