Apple QuickTime RTSP URI Remote Buffer Overflow Vulnerability



Date Discovered

January 1, 2007


Apple QuickTime is prone to a remote buffer-overflow vulnerability because the application fails to properly bounds-check user-supplied input prior to copying it to an insufficiently sized stack-based memory buffer. Exploiting this issue allows remote attackers to execute arbitrary machine code in the context of the affected application, facilitating the remote compromise of affected computers. Attackers exploit this issue by coercing targeted users to access malicious HTML or QTL files or by executing malicious JavaScript code. QuickTime 7.1.3 is vulnerable to this issue; other versions may also be affected.

Technologies Affected

  • Apple QuickTime Player 7.0.4
  • Apple QuickTime Player 7.1.3


Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may reduce the chance of this issue being exploited.

Run all software as a nonprivileged user with minimal access rights.
Invoke all client software with the least privileges required to function. This will limit the effects of a successful compromise.

Do not follow links provided by unknown or untrusted sources.
Do not follow URIs or access files that originate from untrusted sources.

Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.

The vendor has released updates to address this issue. NOTE: Reports indicate that the Windows QuickTime software update will not fix this issue. Users are required to manually patch the affected software from a separately installed updater tool. Please see the references for more information.



LMH is credited with the discovery of this issue.

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.