Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

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
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.