Vulnerabilities play only a tiny role in the security risks that come with mobile phones

Posted by   Martijn Grooten on   Nov 9, 2017

Last week saw yet another successful edition of Mobile Pwn2Own, the contest in which participants are challenged to attack fully patched mobile devices using previously unknown vulnerabilities.

mobilepwn2ownlogo.jpg

Contests like these, and their desktop equivalents, serve two purposes: device manufacturers have vulnerabilities responsibly disclosed to them, while offensive security researchers are able to show off their skills, and get a nice cash prize as a bonus.

One possible message to be taken away from the contest is that every single device ended up getting "pwned"; another, however, would be that it has become increasingly hard to do so. In the case of the Samsung Galaxy S8, for example, it took the attackers no fewer than eleven vulnerabilities to execute code and maintain persistence on the device.

But both of these messages miss the point regarding the way in which almost all attacks against mobile devices happen: they don't exploit known or unknown vulnerabilities, rather they exploit the human factor.

In a typical "attack", the phone's owner is tricked into installing an app, either because it is supposedly necessary, because it promises great things, or maybe just because it is indistinguishable from the real app – which is what made one million users install a rogue version of WhatsApp.

And this is also why, no matter what Pwn2Own's results may suggest, iPhone remains the more secure mobile operating system. Not because of inherent properties of the system itself, but because its strictly controlled environment does a far better job at protecting its users against themselves, even if this protection comes at a cost: earlier this year, Apple decided its Chinese users needed to be "protected" against the use of VPNs.

This does not make iPhones 100% secure though, and we have seen a few cases where an iPhone zero-day was used to compromise the device of a very few targets. But such attacks are rare, and for almost all users attacks like this are a much smaller risk than the chance of they themselves inadvertently opening up their device to an adversary. This is the reason why, for users that are a high-value target, I always recommend an iPhone or a similarly locked-down device (even if I myself am perfectly happy with my Android phone).

And it is also why I believe that using a third-party security app to augment a device's security is a very sensible thing to do, especially on Android, even while acknowledging the limited powers such apps have by design.

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2021 localhost call for last-minute papers

The call for last-minute papers for VB2021 localhost is now open. Submit before 20 August to have your paper considered for one of the slots reserved for 'hot' research!

New article: Run your malicious VBA macros anywhere!

Kurt Natvig explains how he recompiled malicious VBA macro code to valid harmless Python 3.x code.

New article: Dissecting the design and vulnerabilities in AZORult C&C panels

In a new article, Aditya K Sood looks at the command-and-control (C&C) design of the AZORult malware, discussing his team's findings related to the C&C design and some security issues they identified.

VB2021 localhost call for papers: a great opportunity

VB2021 localhost presents an exciting opportunity to share your research with an even wider cross section of the IT security community around the world than usual, without having to take time out of your work schedule (or budget) to travel.

New article: Excel Formula/Macro in .xlsb?

In a follow-up to an article published last week, Kurt Natvig takes us through the analysis of a new malicious sample using the .xlsb file format.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.