Commentary

George Hulme
 

iPhone 3.0 Software Sports Snazzy New Features, Sure: It Also plugs a Whopping 46 Security Flaws

The nearly four dozen security holes filled in the iPhone 3.0 software published by Apple yesterday have gone nearly ignored with all of the buzz surrounding the new features. But these flaws aren't anything you want to put on hold.

The nearly four dozen security holes filled in the iPhone 3.0 software published by Apple yesterday have gone nearly ignored with all of the buzz surrounding the new features. But these flaws aren't anything you want to put on hold.Check it out: 46 vulnerabilities in all. Some of these security flaws are almost a year old, such as CVE-2008-2320.

Many of these flaws, including CVE-2008-3623, CVE-2009-0145, CVE-2009-0146, CVE-2009-0147, CVE-2009-0165, CVE-2009-0155, CVE-2009-1179, CVE-2009-0946, CVE-2009-0040, CVE-2008-3281, CVE-2008-3529, CVE-2008-4409, CVE-2008-4225, CVE-2008-4226, CVE-2008-2320, CVE-2009-0945, CVE-2009-1686, CVE-2009-1687, CVE-2009-1690, CVE-2009-1698, and CVE-2009-1701 -- can all lead to "arbitrary code execution" -- which, in security speak, means "the attacker can run whatever code they please on your device."


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Many of the flaws involve WebKit, CoreGraphics, and Safari. Complete details are available on Apple's support page.

I enjoy my iPhone -- but with this many software vulnerabilities being dumped all at the same time, and most likely timed with the 3.0 release to avoid much scrutiny -- I wouldn't sanction these devices for corporate use.

To make matters worse, it seems those running the iPod touch software have to pay $10 for the upgrade -- which means if they use their iPod touch to check e-mail or surf the Web -- they're vulnerable to all of these flaws. One shouldn't have to pay to have to security-related software defects fixed.

An e-mail to Apple asking whether iPod users can get the security update -- without having to pay for the privilege -- when unanswered by Apple PR.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links