(Apple Issues Fix for iPhone) Apple CoreGraphics Memory Corruption Error Lets Remote Users Execute Arbitrary Code
|
|
SecurityTracker Alert ID: 1021265 |
|
SecurityTracker URL: http://securitytracker.com/id/1021265
|
|
CVE Reference:
CVE-2008-2321
(Links to External Site)
|
Date: Nov 21 2008
|
Impact:
Execution of arbitrary code via network, User access via network
|
Fix Available: Yes Vendor Confirmed: Yes
|
Version(s): 1.0 - 2.1
|
Description:
A vulnerability was reported in Apple CoreGraphics. A remote user can cause arbitrary code to be executed on the target user's system. Apple iPhone is affected.
A remote user can create a specially crafted HTML that, when loaded by the target user, will trigger a memory corruption error in CoreGraphics and execute arbitrary code on the target system.
Other applications that pass untrusted input to CoreGraphics may be able to be used to exploit this.
Michal Zalewski of Google reported this vulnerability.
|
Impact:
A remote user can create HTML that, when loaded by the target user, will execute arbitrary code on the target user's system.
|
Solution:
Apple has issued a fixed version (2.2) of iPhone, which is affected by this vulnerability.
The Apple advisory is available at:
http://support.apple.com/kb/HT3318
|
Vendor URL: support.apple.com/kb/HT3318 (Links to External Site)
|
Cause:
Access control error
|
Underlying OS:
|
|
Message History:
This archive entry is a follow-up to the message listed below.
|
Source Message Contents
|
Date: Fri, 21 Nov 2008 02:46:59 -0500
Subject: Apple iPhone
|
APPLE-SA-2008-11-20 iPhone OS 2.2 and iPhone OS for iPod touch 2.2
CoreGraphics
CVE-ID: CVE-2008-2321
Available for: iPhone OS 1.0 through 2.1,
iPhone OS for iPod touch 1.1 through 2.1
Impact: Visiting a maliciously crafted website may lead to an
unexpected application termination or arbitrary code execution
Description: CoreGraphics contains memory corruption issues in the
processing of arguments. Passing untrusted input to CoreGraphics via
an application, such as a web browser, may lead to an unexpected
application termination or arbitrary code execution. This update
addresses the issue through improved bounds checking. Credit to
Michal Zalewski of Google for reporting this issue.
|
|
