2005-07-01
Abstract
looks at security issues related to mobile phones running on the Windows OS
Copyright © 2005 Virus Bulletin
So, I got myself a smartphone with a 400 MHz Intel Xscale CPU, 128 MB of memory and a fast, EV-DO Internet connection that hits 7-800kbit/s at times. It's brilliant. With it, you can load and edit Word and Excel files, run a fair few executables and read your email, as well as wonder why website designers don't take into account us poor sods with 320 x 240 screens (yes, I know about Bitstream Thunderhawk and its 800 x 600 virtual resolution display).
Sites do load fast though, even if I can't actually make out a great deal of many. On top of that, the music, video, MSN IM, and Skype capabilities mean that I hardly ever use the smartphone for making mobile phone calls.
The phone is, however, a device that runs Windows as its operating system. More specifically, Windows Mobile 2003 Second Edition build 14132. I'm cool with that, but where's that Windows Update function to keep it safe and sound? After all, it does run Internet Explorer (albeit sans active content) and Outlook.
Before the current smartphone, I had another one that ran (and still runs) Windows for Pocket PC 2002. However, I can't upgrade that to Windows Mobile 2003 SE.
Does this lack of updates mean that Microsoft's programmers have created an impenetrable device with which I can stumble around the Internet? I understand that this is an entirely different hardware platform from Intel IA32, but still, it has a powerful processor and fast Internet access, so surely it must be a juicy target for malware writers.
I decided to put my concerns to Microsoft. My first port of call was Microsoft's New Zealand office (MSNZ), where I was told that it is the vendor and/or the device manufacturer's responsibility to furnish customers with updates. Next, I tried contacting the vendor and the manufacturer of the smartphone with my concerns, but drew a blank with both, so I went back toMicrosoft with my doubts.
This time around, Brett Roberts, MSNZ's manager of platform strategy and security, took some time to explain how it all works and to allay my fears of a hacked smartphone with thousand dollar bills (the monopoly telco in New Zealand charges an arm and a leg for mobile data).
First, Brett told me: 'the first thing to consider is the difference between Windows Mobile and our operating system on the desktop, and in turn the resulting difference in upgrade venues and frequency.'
He added: 'Microsoft's relationship with PC owners is direct in many ways - we update software through Windows Update. In the mobile world the operator or device maker owns the device image and is responsible for updating the software.'
He was keen to stress Microsoft's dedication to improving software and security though, saying, 'I stress that Microsoft is continually updating its software and providing updates to operators and OEMs which they, in turn, can use for new devices and those already in the hands of customers. The updates we provide are mostly based upon direct customer (OEM, Operator) feedback in terms of 'fixes'.'
I didn't feel that the answers I had been given had really told me very much, so I decided to fire some more specific questions at Brett regarding smartphone updating. In the following dialogue I am Mr Q, and Brett is Mr A.