Security in Context: The BeyondTrust Blog

Welcome to the Zeroday Tracker: Your Vulnerability Watchlist

Get critical updates on the latest zeroday threats, including impact, mitigation and protection information - only from BeyondTrust.

Apple QuickTime RTSP URL Buffer Overflow

Disclosed January 1, 2007    Fully Patched

Vulnerability Description:

A stack-based buffer overflow occurs when processing a long rtsp:// URL within a QTL file, which is an XML document laid out like the following, according to the published proof-of-concept:

<?xml version="1.0"?>
<?quicktime type="application/x-quicktime-media-link"?>
 src="rtsp://A:[258 or more characters]" />

This malicious QTL file may be hosted on a web site, allowing for exploitation across the internet. Other attack vectors may be possible to reach the same vulnerable code in QuickTime which may require less user interaction than this published proof-of-concept.



Vulnerable Software/Devices:

QuickTime 7.1.3 and earlier

Vulnerability Severity:


Exploit Availability:


BeyondTrust Prevention and Detection:

BeyondTrust's Blink® Personal Edition protects from this vulnerability.
BeyondTrust's Blink® Professional Edition protects from this vulnerability.

Security Update 2007-001


A vendor-supplied patch is available and is the best form of mitigation for this vulnerability.

Previous Mitigation Information
To block the published proof-of-concept using other mitigation, users are suggested to disassociate QTL files from QuickTime. This can be accomplished via the registry, by editing the (default) key in HKEY_CLASSES_ROOT.qtl. Simply adding a ".bak" will disable QuickTime from opening QTL files. This mitigation will only protect from the QTL-file vector, which is the only published attack vector.
NOTE: Although some sources have suggested disabling RTSP within QuickTime, this does not effectively stop the proof-of-concept exploit.


Original Disclosure (MoAB-01-01-2007)
PoC Code Disclosure - Mac (Non-Malicious Exploit)
PoC Code Disclosure - Windows (BindShell TCP/4444)



Leave a Reply