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.

Risk

9/15/2009
06:14 PM
Jake Widman
Jake Widman
Commentary
50%
50%

iPhone Security Fix May Reveal Longstanding Vulnerability

The latest release of the OS for iPhones and iPod Touches breaks the Microsoft Exchange Server compatibility of many existing devices. In doing so, it may have revealed that businesses that trusted Apple's assurances about the devices' security were misled.

The latest release of the OS for iPhones and iPod Touches breaks the Microsoft Exchange Server compatibility of many existing devices. In doing so, it may have revealed that businesses that trusted Apple's assurances about the devices' security were misled.Version 3.1 of the iPhone OS, released last week, apparently fixes a security vulnerability in the previous version that came out last June. But in so doing, it has uncovered what some observers believe to have been deceptive practices by Apple for more than a year. Users who installed the new version on pre-GS iPhones and iPod Touches suddenly found that they could no longer connect to their companies' Exchange servers. When they tried, they got an error message saying that "the account [name] requires encryption which is not supported on this iPod/iPhone."

The encryption requirement is set on the Exchange side, and the wording of the message indicates that the device itself is unable to support encryption, period. The problem is, many iPhone owners have been blithely accessing Exchange servers with that requirement since July 2008, when iPhone 2.0 added that capability. One conclusion is that the iPhone has been confirming to Exchange that it supported encryption when in fact it did not, meaning that business users have been toting around insecure data all this time while thinking they were meeing their company's security policies.

At the moment, there are three fixes for the immediate problem: first, have your company remove the encryption requirement from Exchange. Few companies who bothered to establish that requirement in the first place are likely to remove it just to support old iPhones. Second, replace your iPhone with a new iPhone 3GS -- a great solution from Apple's standpoint, but not so great for a cost-conscious business. Or third, downgrade your iPhone to version 3.0 of the OS if you still have it. That'll restore access to your Exchange server, but if that access was enabled by false confirmation from the iPhone, this approach won't solve the security problem.

So far, Apple has not addressed the issue, so we don't know whether the OS can be modified to support encryption on older devices, or indeed whether those devices can manage encryption at all. This episode highlights in a dramatic fashion the headaches that come with the consumerization of business technology, particularly the addition of personal smartphones to the workplace systems mix. Even more, it raises issues of trust for Apple. As a booster of Apple solutions for small and midsize businesses, I'll be watching closely to see if the company acknowledges and addresses the issue.

Don't Miss: Help Arrives to Secure Mobile Devices

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-7505
PUBLISHED: 2020-02-18
Stack-based buffer overflow in the gif_next_LZW function in libnsgif.c in Libnsgif 0.1.2 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted LZW stream in a GIF file.
CVE-2015-7567
PUBLISHED: 2020-02-18
SQL injection vulnerability in Yeager CMS 1.2.1 allows remote attackers to execute arbitrary SQL commands via the "passwordreset&token" parameter.
CVE-2012-0718
PUBLISHED: 2020-02-18
IBM Tivoli Endpoint Manager 8 does not set the HttpOnly flag on cookies.
CVE-2019-10791
PUBLISHED: 2020-02-18
promise-probe before 0.10.0 allows remote attackers to perform a command injection attack. The file, outputFile and options functions can be controlled by users without any sanitization.
CVE-2009-5146
PUBLISHED: 2020-02-18
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.