Risk
6/30/2010
04:26 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Which Platform Is Safer: Android, Blackberry, or iPhone?

With the hand-held platform battle over market share heating up, more people are wondering just which platforms may be safer from attackers and snoops.

With the hand-held platform battle over market share heating up, more people are wondering just which platforms may be safer from attackers and snoops.Gartner analyst John Pescatore posed the question in his blog last Friday, likening some smart phone platforms to the PCs open platform and others to the more locked-down mainframe. Pescatore noted that, so far, the smart phones with more closed eco-systems are the most popular. Here's what he had to say:

• Blackberry - a very tightly controlled platform, very limited ability for users to create, install and share applications. Great from a security perspective, but in reality the Blackberry gained market share because it was the first portable email+phone device and not really because of the smartphone/application side of things.

• Windows Mobile - as you would expect, Microsoft took the approach of making a tiny, little handheld PC with a cellphone buried inside. Lots more freedom for users to install and share applications, but not all that successful in the marketplace.

• iPhone - the iPhone really is a little tiny mainframe. It is a closed platform, Apple decides what applications get on the whitelist (the App Store) but it is a really, really big whitelist - users don't notice the boundaries. It is like when you put a goldfish in a bathtub - "I'm free!!" shouts the goldfish. Life can be pretty good, security-wise, if you can keep all your users in a bathtub.

As Pescatore noted, the Droid OS is designed to closely resemble the PC and its open ability to run lots of applications not vetted by a central authority. That fact could quite possibly open the phone to the same types of malware that have plagued PCs for generations now. And if an analysis from mobile security firm SMobile Systems, released last week, of more than 48,000 applications available on the Android is correct: that is exactly what could happen:

• 20 percent of applications in the Android market grant a third party application access to private or sensitive information that an attacker could use for malicious purposes, such as Identity Theft, mobile banking fraud and corporate espionage; 5 percent of applications have the ability to place a call to any number, without requiring user intervention;

• 2 percent of market submissions can allow an application to send unknown premium SMS messages without user intervention.

That data certainly doesn't look good for Android. And Google undoubtedly needs to take additional steps to limit the amount of access applications have to other areas of the platform, and what can be done without user intervention.

But this doesn't mean other platforms such as iPhone and Blackberry are safe, either.

In February a senior security researcher for Veracode demonstrated how using the RIM API (and without leveraging any software exploits or Blackberry vulnerabilities) was able to snoop nearly at-will on the device. Then, when it comes to the iPhone, developer Nicolas Seriot in December released a proof-of-concept application, SpyPhone, that demonstrated how the public iPhone API can be used to grab data from other applications, such as the keyboard cache or address book.

The safe assumption is that the phone platform you use isn't less, or more, secure than any others: and take caution on the Web sites you visit and the applications you install.

For my security and technology observations throughout the day, find me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-5084
Published: 2015-08-02
The Siemens SIMATIC WinCC Sm@rtClient and Sm@rtClient Lite applications before 01.00.01.00 for Android do not properly store passwords, which allows physically approximate attackers to obtain sensitive information via unspecified vectors.

CVE-2015-5352
Published: 2015-08-02
The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time ...

CVE-2015-5537
Published: 2015-08-02
The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566.

CVE-2015-5600
Published: 2015-08-02
The kbdint_next_device function in auth2-chall.c in sshd in OpenSSH through 6.9 does not properly restrict the processing of keyboard-interactive devices within a single connection, which makes it easier for remote attackers to conduct brute-force attacks or cause a denial of service (CPU consumptio...

CVE-2015-1009
Published: 2015-07-31
Schneider Electric InduSoft Web Studio before 7.1.3.5 Patch 5 and Wonderware InTouch Machine Edition through 7.1 SP3 Patch 4 use cleartext for project-window password storage, which allows local users to obtain sensitive information by reading a file.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!