EEYEB-20051117B Apple iTunes (QuickTime.qts) Heap Overflow
January 10, 2006
November 17, 2005
Patch Development Time (In Days):
High (Code Execution)
Quicktime on Windows 2000
Quicktime on Windows XP
Quicktime on Mac OS X 10.3.9
Apple iTunes on Windows 2000
Apple iTunes on Windows XP
Apple iTunes on OS X 10.3.9
eEye Digital Security has discovered a critical vulnerability in Apple
iTunes. The vulnerability allows an attacker to reliably overwrite heap
memory with user-controlled data and execute arbitrary code in the
context of the user who executed iTunes.
This specific flaw exists within the QuickTime.qts file which many
applications access QuickTime's functionality through. By specially
crafting atoms within a movie file, a direct heap overwrite is
triggered, and reliable code execution is then possible.
The code in QuickTime.qts responsible for copying Movie Resource atom
type sizes in a QuickTime-format movie into an array allocated on the
heap. According to developer.apple.com, the format of the Movie Resource
atom is as follows:
Atom Size 4 bytes
Atom Type 4 bytes
By supplying the .MOV file with a large atom size results in a
insufficiently-sized heap block to be allocated, resulting in a complete
heap memory overwrite ultimately failing in the List_Component()
QuickTime: QuickTime File Format
Apple has released a patch for this vulnerability. The patch is
available via the Updates section of the affected applications.
This vulnerability has been assigned the CVE identifier CAN-2004-0431.
Discovery: Karl Lynn
Copyright (c) 1998-2006 eEye Digital Security
Permission is hereby granted for the redistribution of this alert
electronically. It is not to be edited in any way without express
consent of eEye. If you wish to reprint the whole or any part of this
alert in any other medium excluding electronic medium, please email
alert (at) eEye (dot) com [email concealed] for permission.
The information within this paper may change without notice. Use of this
information constitutes acceptance for use in an AS IS condition. There
are no warranties, implied or express, with regard to this information.
In no event shall the author be liable for any direct or indirect
damages whatsoever arising out of or in connection with the use or
spread of this information. Any use of this information is at the user's