QuickTime full changelog

Impact: Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution
Description: Multiple memory corruption issues existed in QuickTime. These issues were addressed through improved memory handling

Impact: Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution
Description: Multiple memory corruption issues existed in QuickTime. These issues were addressed through improved memory handling

Processing a maliciously crafted file may lead to an unexpected application termination or arbitrary code execution
Multiple memory corruption issues existed in QuickTime. These issues were addressed through improved memory handling.

Improves security and is recommended for all QuickTime 7 users on Windows.

An uninitialized pointer issue existed in the handling of track lists. This issue was addressed through improved error checking.
A buffer overflow existed in the handling of H.264 encoded movie files. This issue was addressed through improved bounds checking.
An out of bounds byte swapping issue existed in the handling of QuickTime image descriptions. This issue was addressed through improved bounds checking.
A signedness issue existed in the handling of 'stsz' atoms. This issue was addressed through improved bounds checking.

# An uninitialized pointer issue existed in the handling of track lists. This issue was addressed through improved error checking.
# A buffer overflow existed in the handling of H.264 encoded movie files. This issue was addressed through improved bounds checking.
# An out of bounds byte swapping issue existed in the handling of QuickTime image descriptions. This issue was addressed through improved bounds checking.
# A signedness issue existed in the handling of 'stsz' atoms. This issue was addressed through improved bounds checking.
# A buffer overflow existed in the handling of 'ftab' atoms. This issue was addressed through improved bounds checking.
# A memory corruption issue existed in the handling of 'dref' atoms. This issue was addressed through improved bounds checking.
# A buffer overflow existed in the handling of 'ldat' atoms. This issue was addressed through improved bounds checking.

· Opening a maliciously crafted TeXML file may lead to an unexpected application termination or arbitrary code execution. A memory corruption issue existed in the handling of TeXML files. This issue was addressed through improved bounds checking.
· Playing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in the handling of H.263 encoded movie files. This issue was addressed through improved bounds checking.
· Playing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in the handling of 'dref' atoms. This issue was addressed through improved bounds checking.
· Playing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in the handling of H.264 encoded movie files. This issue was addressed through improved bounds checking.

· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in QuickTime's handling of H.264 encoded movie files.
· Viewing a maliciously crafted movie file may lead to the disclosure of memory contents. An uninitialized memory access issue existed in QuickTime's handling of URL data handlers within movie files.
· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. An implementation issue existed in QuickTime's handling of the atom hierarchy within a movie file
· An attacker in a privileged network position may inject script in the local domain when viewing template HTML. A cross-site scripting issue existed in QuickTime Player's quot;Save for Webquot; export. The template HTML files generated by this feature referenced a script file from a non-encrypted origin.

· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in QuickTime's handling of H.264 encoded movie files.
· Viewing a maliciously crafted movie file may lead to the disclosure of memory contents. An uninitialized memory access issue existed in QuickTime's handling of URL data handlers within movie files.
· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. An implementation issue existed in QuickTime's handling of the atom hierarchy within a movie file
· An attacker in a privileged network position may inject script in the local domain when viewing template HTML. A cross-site scripting issue existed in QuickTime Player's quot;Save for Webquot; export. The template HTML files generated by this feature referenced a script file from a non-encrypted origin.

· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. A buffer overflow existed in QuickTime's handling of H.264 encoded movie files.
· Viewing a maliciously crafted movie file may lead to the disclosure of memory contents. An uninitialized memory access issue existed in QuickTime's handling of URL data handlers within movie files.
· Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. An implementation issue existed in QuickTime's handling of the atom hierarchy within a movie file
· An attacker in a privileged network position may inject script in the local domain when viewing template HTML. A cross-site scripting issue existed in QuickTime Player's quot;Save for Webquot; export. The template HTML files generated by this feature referenced a script file from a non-encrypted origin.