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.


04:48 PM
George V. Hulme
George V. Hulme

Cell Phone New Cybercrime Frontline

Whether it's your iPhone, Windows Mobile device, Android, or BlackBerry -- you're probably using your smartphone more like a computer more and more. That's great, but the more your phone acts like a PC -- the more likely all of the problems associated with PCs will follow, researchers said today. Should you care?

Whether it's your iPhone, Windows Mobile device, Android, or BlackBerry -- you're probably using your smartphone more like a computer more and more. That's great, but the more your phone acts like a PC -- the more likely all of the problems associated with PCs will follow, researchers said today. Should you care?We've been warning about the security of mobile devices for years, and years, and years. I've written so many stories about the security risks of mobile phones that I'm starting to feel like Chicken Little. So far, we've not seen a major virus or malware event. That doesn't mean it's not going to happen. The infamous Morris worm hit in 1988 -- and we didn't see a similar event at any time in the 1990s. Viruses were a problem, but they didn't become a really big humungo problem until the LoveBug overloaded e-mail servers in the spring of 2000.

These things don't always happen when we first expect them. But we can see the trend lines: more criminals are turning to cybercrime to steal, snoop, and destroy; and smartphones are growing exponentially in processing and storage power. We're also starting to see smartphones with more open, generative platforms, such as Google's Android.

It's a safe bet to predict these two trend lines will cross, and criminals will turn to mobile phones to conduct all of the types of crimes they do on PCs and the Internet today. Predicting exactly when this will happen: not so easy.

Researchers contributing to Georgia Tech's Emerging Cyber Threats Report for 2009: Data, Mobility, and Questions of Responsibility Will Drive Cyber Threats in 2009 And Beyond, see the risks.

The comments below, from the report, are from Patrick Traynor assistant professor at the School of Computer Science at Georgia Tech:

According to Traynor, "malware will be injected onto cell phones to turn them into bots. Large cellular botnets could then be used to perpetrate a DoS attack against the core of the cellular network. But because the mobile communications field is evolving so quickly, it presents a unique opportunity to design security properly -- an opportunity we missed with the PC."

Traynor pointed out that most people buy a new mobile device every two years -- a much shorter life cycle than the typical PC and Windows installation, which is closer to 10 years.

"The short life cycle of mobile devices gives manufacturers, developers, and the security community an opportunity to learn what works from a security standpoint and apply it to devices and applications more quickly," said Traynor. "However, it is not going to be an easy problem to solve."

Tom Cross, X-Force Researcher with IBM Internet Security Systems, along with Traynor, cites Google's Android -- because of it's openness, it makes it easier for security vendors to build defenses for the device. On that, I agree. However, it also makes it much easier for malware authors, as well. Which means we'll be in the same PC security arms race we've experienced for more than 20 years now.

The ultimate solution is what both Traynor and Cross stated in their closing thought: a layered approach to security on mobile devices that encompasses carriers, manufacturers, and application developers.

That type of industry security synergy is exactly the best shot we have at ensuring smart phones don't become the battleground we're now fighting on PCs and corporate networks.

It's also expensive and difficult to get all of these constituents to work so closely together.

It may happen. But my prediction is that it's going to take a significantly enough nasty event for the industry to come together that tightly over security concerns.

Check out the Georgia Tech's Emerging Cyber Threats Report for 2009, available here.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-12-04
In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43...
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.