nCircle.com >> 360 Security >> The Lens

« A Virtual Advantage | Main

iPhone 2.0 is Less Secure

There's nothing quite as effective for illustrating a point than a top n list. Here are the top 4 reasons that the new iPhone is less secure than the previous version.

4. The Price

How could the price make the product less secure? Very simply, the more ubiquitous a platform, the more attractive a target it is. By lowering the price in order to increase market-share, Apple is creating a more attractive base of targets.

3. The SDK

Complexity breeds insecurity. The addition of third party code creates an avenue for exploit. Apple can work to minimize that, but there's a choice of functionality over security here. After all, not shipping the product at all would be very secure.

2. MS Office Compatibility

Do you remember MS08-026? How about MS07-044? Well, welcome to the world of remote code execution via MS Office Documents, little iPhone.

1. Enterprise-Ready

If the price of the iPhone increases its attractiveness as a target due to volume, then being enterprise-ready increases its attractiveness due to value. All the things about other enterprise computing devices that attackers love will now be present in the iPhone. Along with that comes a whole new world of exciting hackability. Who wouldn't want to break into it and see what juicy data the CEO is storing there?

TrackBack

TrackBack URL for this entry:
http://blog.ncircle.com/cgi-bin/mt-tb.cgi/279

Comments (5)

Alex:

I agree that there is the potential for more *risk* with the new iPhone, but fail to understand how the price of something or anticipated market penetration can cause it to be less resistant to the force applied by a threat community.

Ah, semantics. You're defining the adjective 'secure' as (a measure of) 'resistance to the force applied by a threat community.' You're not defining risk at all, but I'll presume you mean some reasonable definition that combines threat, probability and severity.

In those terms, we agree. I'm pointing out that the increased distribution of the iPhone platform increases the probability of attack because it's a more available target. I'm also pointing out that the 'enterprise readiness' of the platform increases the potential for data loss (severity?) of any successful attack, as well as increasing the probability of attack. In other words, yes, increased risk through changes in probability and severity.

I would argue that an increase in the amount of risk (noun) results in an object being less secure (adjective).

txs:

Likelihood of exploit and or type of data located on the device does not modify the security level of the object itself. The security of an object when compared against specific attack scenarios is a pass fail model. Enumeration of these threat vectors and looking at possible success determines the security level of the object.

When looking at risk levels I agree fully that you have to include the chance of exploit as well the sensitivity of the data being secured. However, when looking at the individual security of a device against specific attacks, the likelihood nor the data stored matters.

I agree with Alex here. Either way we may simply be running into a matter of semantics.

4. The Price: I don't know that price, one way or another, would make it any more or less a target just because of the necessity to sign a contract to get one. Sure, availability is better (which is obviously the plan from a business standpoint) but I tend to think that the people who want to play with the potential for exploiting iPhone security would do so regardless of price.

3. The SDK: Apple has done a pretty decent job of sandboxing 3rd party apps from the rest of the OS. So much so that it's actually a bit of a pain to us developers from a functionality standpoint. Of course nothing is 100% secure, and it's only going to be a matter of time before some clever coder punches through the sandbox.

2. MS Office Compatibility: This I disagree with very much. The vulnerabilities you've referenced are more issues with Word and Excel themselves, not necessarily the document format. Of course there's the occasional one-off format-based vulnerability (remember WMF?), but the simple fact that something understands how to read the .doc format doesn't magically make it vulnerable to every exploit written for Microsoft Word. Google Docs, iWork, OpenOffice, Abiword, the list goes on.

1. Enterprise-Ready: I don't even understand this point. This is part of the risk of any commercial product. The iPhone is no more or less special than any other device with significant market penetration, be it Enterprise-level or general consumer.

4. The point here isn't that a lower price puts it in the hands of more potential hackers, but that a wider user base makes it a more attractive target.

3. Yep, I agree.

2. I'm not sure I agree with you here. While a 'reader' application may have fewer avenues for exploit because it's a less complex piece of code, the existing popularity of MS Office documents as an attack vector definitely increases the likelihood that it will be used as such on the iPhone as well.

1. The point here isn't that the iPhone is special or different. It was different in that it didn't support standard enterprise features. It's now less different, perhaps. Still, further penetration into the enterprise increases the likely value of the information stored on the device. Combine that increased value with wider distribution, and you have a much more attractive target that the previous iPhone.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About

This page contains a single entry from the blog posted on June 10, 2008 1:13 PM.

The previous post in this blog was A Virtual Advantage.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.35