Vulnerability Note VU#687201

Apple QuickTime and iTunes QTIF image buffer overflow

Original Release date: 12 Jan 2006 | Last revised: 20 Jan 2006

Overview

Apple QuickTime contains a heap-based buffer overflow that may allow an attacker to execute arbitrary code or cause a denial-of-service condition.

Description

Apple QuickTime fails to properly validate QuickTime Images (QTIF), potentially allowing a heap-based buffer overflow to occur. If a remote attacker supplies a vulnerable Apple QuickTime installation with a specially crafted QTIF image, that attacker may be able to trigger the buffer overflow. This issue affects QuickTime installations on both Apple Mac and Microsoft Windows operating systems.

Note that since QuickTime is a component of Apple iTunes, iTunes installations are also affected by this vulnerability.

Impact

A remote unauthenticated attacker may be able to execute arbitrary code or cause a denial-of-service condition, if they can persuade a user to access a specially crafted QTIF image.

Solution

Apply Update
Apple has corrected this issue in Apple Security Update for QuickTime 7.0.4.

Do not access QTIF files from untrusted sources


Exploitation occurs by accessing a specially crafted QTIF file with QuickTime. By only accessing QTIF files from trusted or known sources, the chances of exploitation are reduced.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Apple Computer, Inc.Affected-11 Jan 2006
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This issue was reported by Apple Product Security. Apple credits Varun Uppal of Kanbay for reporting this issue.

This document was written by Jeff Gennari.

Other Information

  • CVE IDs: CVE-2005-2340
  • Date Public: 10 Jan 2006
  • Date First Published: 12 Jan 2006
  • Date Last Updated: 20 Jan 2006
  • Severity Metric: 16.40
  • Document Revision: 24

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.