{"id":25006,"date":"2014-04-24T08:50:57","date_gmt":"2014-04-24T15:50:57","guid":{"rendered":"http:\/\/www.intego.com\/mac-security-blog\/?p=25006"},"modified":"2014-04-24T15:48:37","modified_gmt":"2014-04-24T22:48:37","slug":"apple-securing-mac-iphone","status":"publish","type":"post","link":"https:\/\/www.intego.com\/mac-security-blog\/apple-securing-mac-iphone\/","title":{"rendered":"Does Apple care more about securing Mac users than iPhone users?"},"content":{"rendered":"

\"Does<\/p>\n

In the last couple of days, Apple has issued critical security patches for iOS<\/a>, Mac OS X<\/a>, the Apple Airport Base Station<\/a>, and even the innocuous hockey puck-shaped Apple TV<\/a>.<\/p>\n

And I trust, as a regular loyal reader of the Mac Security blog, that you haven’t wasted any time ensuring that all of your devices and gadgets are fully patched up, and protected from potential attack by hackers.<\/p>\n

After all, some of the security flaws tackled by these patches are extremely serious – and could lead to your devices being compromised by malicious hackers, or your personal and private data being stolen.<\/p>\n

But the list of patches above reveals just how many different types of consumer and business gadgets Apple’s security team needs to consider these days when a new flaw is discovered, and raises an important question:<\/p>\n

Does Apple treat all of its products equally when it comes to security?<\/strong><\/p>\n

Sadly, it seems they don’t.<\/p>\n

Take a look at this list of issues that Apple has just fixed in WebKit, the framework that underlies the Safari browser on iPhones and iPads, and the security holes it addressed in the OS X desktop\/laptop version of Safari a full three weeks ago:<\/p>\n\n\n\n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Security updates contained in
\niOS 7.1.1, issued this week<\/th>\n		<\/th>\nSecurity updates in Safari 7.0.3 for OS X, released three weeks ago on 1 April 2014<\/th>\n<\/tr>\n
CVE-2013-2871<\/td>\nmiaubiz<\/td>\n<\/td>\nCVE-2013-2871<\/td>\nmiaubiz<\/td>\n<\/tr>\n
CVE-2014-1298<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2013-2926<\/td>\ncloudfuzzer<\/td>\n<\/tr>\n
CVE-2014-1299<\/td>\nGoogle Chrome Security Team, Apple, Renata Hodovan of University of Szeged \/ Samsung Electronics<\/td>\n<\/td>\nCVE-2013-2928<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1300<\/td>\nIan Beer of Google Project Zero working with HP’s Zero Day Initiative<\/td>\n<\/td>\nCVE-2013-6625<\/td>\ncloudfuzzer<\/td>\n<\/tr>\n
CVE-2014-1302<\/td>\nGoogle Chrome Security Team, Apple<\/td>\n<\/td>\nCVE-2014-1289<\/td>\nApple<\/td>\n<\/tr>\n
CVE-2014-1303<\/td>\nKeenTeam working with HP’s Zero Day Initiative<\/td>\n<\/td>\nCVE-2014-1290<\/td>\nant4g0nist (SegFault) working with HP’s Zero Day Initiative, Google Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1304<\/td>\nApple<\/td>\n<\/td>\nCVE-2014-1291<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1305<\/td>\nApple<\/td>\n<\/td>\nCVE-2014-1292<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1307<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1293<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1308<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1294<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1309<\/td>\ncloudfuzzer<\/td>\n<\/td>\nCVE-2014-1298<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1310<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1299<\/td>\nGoogle Chrome Security Team, Apple, Renata Hodovan of University of Szeged \/ Samsung Electronics<\/td>\n<\/tr>\n
CVE-2014-1311<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1300<\/td>\nIan Beer of Google Project Zero working with HP’s Zero Day Initiative<\/td>\n<\/tr>\n
CVE-2014-1312<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1301<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
CVE-2014-1313<\/td>\nGoogle Chrome Security Team<\/td>\n<\/td>\nCVE-2014-1302<\/td>\nGoogle Chrome Security Team, Apple<\/td>\n<\/tr>\n
CVE-2014-1713<\/td>\nVUPEN working with HP’s Zero Day Initiative<\/td>\n<\/td>\nCVE-2014-1303<\/td>\nKeenTeam working with HP’s Zero Day Initiative<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1304<\/td>\nApple<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1305<\/td>\nApple<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1307<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1308<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1309<\/td>\ncloudfuzzer<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1310<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1311<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1312<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1313<\/td>\nGoogle Chrome Security Team<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\nCVE-2014-1713<\/td>\nVUPEN working with HP’s Zero Day Initiative<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do you see any similarities? Sure, the patch for desktop OS X users contains more fixes than the one for iOS users, but ignore that for now.<\/p>\n

For those of you who haven’t spotted, I’ve shaded in the security holes that are shared between the Mac OS X and iOS versions of Safari in a fetching shade of blue.<\/p>\n

In short, three weeks ago, when it released its security update for OS X, Apple told the world that there were critical security holes in its browser and provided fixes.<\/p>\n

That would have been fine, if it had patched the same underlying vulnerabilities on the iPhone and iPad at the same time. After all, we know that hackers love nothing more than to reverse-engineer security patches and see if the same holes can be used elsewhere. But Apple *didn’t* patch iPhones and iPads at that point.<\/p>\n

Instead, it left those iOS users vulnerable for three weeks.<\/p>\n

And this isn’t a new phenomenon. Time and time again we have seen the iOS operating system used by Apple iPhones and iPads lagging behind – sometimes by months – when it comes to security updates compared to its big brother operating system, Mac OS X.<\/p>\n

Security researcher Kristin Paget took to her blog<\/a> to underline her disapproval of what appears to be Apple treating its millions of iPhone and iPad users as second class citizens, security-wise:<\/p>\n

OK, so the desktop patch also included a few more issues \u2013 but clearly the iOS vulnerabilities they just fixed are a direct subset of the vulnerabilities they fixed 3 weeks ago. Apparently someone needs to sit Apple in front of a chalkboard and make them write out 100 lines:<\/p>\n

\u201cI will not use iOS to drop 0day on OSX, nor use OSX to drop 0day on iOS\u201d.<\/p>\n

Seriously, Apple \u2013 what the ****?<\/p>\n

Is this how you do business? Drop a patch for one product that quite literally lists out, in order, the security vulnerabilities in your platform, and then fail to patch those weaknesses on your other range of products for *weeks* afterwards? You really don\u2019t see anything wrong with this?<\/p><\/blockquote>\n

Paget is quite right.<\/p>\n

A malicious hacker could have taken one of these patched OS X vulnerabilities, and weaponised it for exploitation in a zero-day attack against iPhone and iPad users.<\/p>\n

Every time Apple treats its smartphone and tablet customers as poor relations when it comes to security, they are putting millions of users at risk.<\/p>\n

As we’ve explained before on the Mac Security blog, there are multiple ways in which malicious hackers and cybercriminals can target your systems<\/a>, so remember the importance of a layered approach to security.<\/p>\n

One of the layers is regularly updating your software against vulnerabilities as patches become available. Sadly, it’s evident that you can be doing a faultless job in keeping your systems updated, but still be let down if Apple fails to fix iOS and OS X security issues simultaneously.<\/p>\n","protected":false},"excerpt":{"rendered":"

In the last couple of days, Apple has issued critical security patches for iOS, Mac OS X, the Apple Airport Base Station, and even the innocuous hockey puck-shaped Apple TV. And I trust, as a regular loyal reader of the Mac Security blog, that you haven’t wasted any time ensuring that all of your devices […]<\/p>\n","protected":false},"author":34,"featured_media":25048,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[7,13],"tags":[3151,69,9,174,168,177,115,148],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\t\n\t\n\t\n