iOS apps can be hijacked to show fraudulent content and intercept data
arstechnica.com
arstechnica.com
I mean, I'd love to see more apps capable not only of SSL but certificate pinning, binary data transfer, and more.
Besides we all know in-app communication is low-hanging fruit for security researchers, even with otherwise secure apps. Twitter's hard-coded OAuth token with unlimited usage comes to mind, for example. It's not that the apps themselves aren't "secure enough" but that once you remove the restrictive nature of the browser as sandbox with an exposed address bar, apps can get up to some funny business seemingly out of sight.
A useful reminder, to be sure, but it must be a slow news day for this to get so many up votes.
Oh and the original article mentions creating a certificate profile to install a custom SSL cert. That same technique can be used to MITM Apple's own iMessage system, since iMessage doesn't use certificate pinning: http://www.tripwire.com/state-of-security/top-security-stori...
Though the more "iPhone security vulnerability" stories you hear, it just comes down to fundamental principles. I'd be more worried from a security perspective that jailbreakers still say iOS 7.0.3 is vulnerable.
there, I just saved you from reading the article, and you probably learned more anyway.
I've seen this before from Goodin and Ars Technica. What a shame.
> The weakness, dubbed HTTP request hijacking (HRH), is
> estimated to affect at least 10,000 titles in Apple's
> App Store.
I hate reading numbers like this. How did they arrive at 10,000? It's very easy to "estimate" by making up a number.Editor meeting: "Can you spin this into an Apple story. It will be great for clickthrough rates."
New headline: "iOS apps can be hijacked to show fraudulent content and intercept data"
"Make sure the app interacts with its designated server(s) via an encrypted protocol (e.g., HTTPS, instead of HTTP). As described earlier in the post, this is an effective mitigation for HRH, but not a fix."
but not a fix?