Apple`s iTunes MPEG4 buffer overflow
| apple-itunes-mpeg4-bo (20498) |  High Risk |
Description:
iTunes is vulnerable to a buffer overflow caused by improper bounds checking in the MPEG-4 file parsing. By sending a specially-crafted MPEG4 file, a remote attacker could overflow a buffer and execute arbitrary code on the system with user privileges or cause a denial of service.
Platforms Affected:
- Apple, iTunes 4.2.72
- Apple, iTunes 4.5
- Apple, iTunes 4.6
- Apple, iTunes 4.7
- Apple, iTunes 4.7.1
Remedy:
Upgrade to the latest version of MacOS X (10.2.8 or later), as listed in AppleCare Knowledge Base Article ID 61798. See References.
Consequences:
Gain Access
References:
- AppleCare Knowledge Base Article ID 301596, iTunes 4.8: Security enhancements at http://docs.info.apple.com/article.html?artnum=301596.
- AppleCare Knowledge Base Article ID 61798, Apple security updates at http://docs.info.apple.com/article.html?artnum=61798.
- CIAC INFORMATION BULLETIN P-201, iTunes MPEG4 Parsing Buffer Overflow at http://www.ciac.org/ciac/bulletins/p-201.shtml.
- BID-13565: Apple iTunes MPEG4 Parsing Buffer Overflow Vulnerability
- CVE-2005-1248: Buffer overflow in Apple iTunes before 4.8 allows remote attackers to execute arbitrary code via a crafted MPEG4 file.
- OSVDB ID: 16243: Apple iTunes MPEG-4 File Parsing Overflow
- SA15310: iTunes MPEG-4 File Parsing Buffer Overflow Vulnerability
- SECTRACK ID: 1013927: Apple iTunes MPEG4 Buffer Overflow May Let Remote Users Execute Arbitrary Code
- VUPEN/ADV-2005-0504: Apple iTunes MPEG4 File Parsing Buffer Overflow Vulnerability
Reported:
May 09, 2005
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net