Vulnerabilities / Threats
7/2/2009
03:13 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Apple Planning Fix For iPhone SMS Flaw

An SMS vulnerability in Apple's iPhone is slated for disclosure at the Black Hat conference later this month. Apple is reportedly rushing to get a fix ready.

Apple is reportedly working to fix an SMS message handling vulnerability in its iPhone that could be used by an attacker to run unauthorized code with full access to the device.

According to IDG News Service, Apple has been notified about the vulnerability and is working on a patch that's planned for release prior to the Black Hat USA security conference later this month.

Apple did not immediately respond to a request for comment. But iPhone vulnerabilities are not unheard of: The company's recent iPhone 3.0 software release included 46 fixes for security vulnerabilities.

At Black Hat, which runs from July 25-30 in Las Vegas, Charlie Miller, a security researcher with Independent Security Evaluators, plans to present information about the vulnerability.

Miller mentioned the vulnerability in an iPhone security presentation on Thursday at the SyScan security conference in Singapore, but declined to provide details, citing an agreement with Apple, IDG reports.

Miller was not immediately available to comment.

He plans to participate in two presentations at Black Hat: "Post Exploitation Bliss: Loading Meterpreter on a Factory iPhone" and "Fuzzing the Phone in your Phone."

The former talk will explain how to inject unsigned code into an iPhone's process address space. The latter will explore how to inject SMS messages into iPhones, Android phones, and Windows Mobile devices using a technique called fuzzing.

Both this year and last, Miller has won Apple hardware at the CanSecWest security conference's Pwn2Own contest by exploiting previously unknown vulnerabilities in Apple's Safari Web browser.

Black Hat is owned by TechWeb, which also publishes InformationWeek.

InformationWeek has published an in-depth report on smartphone security. Download the report here (registration required).

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.