You expected a patch in just 10 business days (2 business weeks)? Once
they determine what solution to implement and the code change needed for
that solution, then they have to regression test the change on every
vulnerable version of Windows in which a version of DirectX is affected.
That code change may need to be incorporated in MANY versions of DirectX
starting with the first version of it that is supported on the
vulnerable versions of Windows. Wow, you don't ask for much.
"In a Web-based attack scenario, an attacker would have to host a Web
site that contains a Web page that is used to exploit this
vulnerability. An attacker would have no way to force users to visit a
malicious Web site. Instead, an attacker would have to convince them to
visit the Web site, typically by getting them to click a link that takes
them to the attacker's Web site."
You might want to stick with well-known, highly-trafficked, and trusted
sites in the meantime. No "blue movie" sites for you for awhile. >;->
Do you actually visit sites using QT video formats? I can find them but
I have to actually go search for them. When I wanted to test a QT
install, I knew a couple of game sites with video movies of previews or
gameplays but they switched to Flash.
My first thought was to reassociate the Quicktime filetypes back to the
QuickTime Player and have it play those files. Guess that won't help.
According to Microsoft's Security Research & Defense blog at
http://blogs.technet.com/srd/archive/2009/05/28/new-vulnerability-in-quicktime-parsing.aspx,
"whether youʼve installed Appleʼs QuickTime or not, the vulnerability is
in the Microsoftʼs quartz.dll and itʼs possible to craft an attack to
call that DLL on the system regardless of whether Appleʼs QuickTime is
present."
Guess you can perform the workarounds that the Microsoft advisory
suggests or wait until a patch is released and be paranoid in the
meantime (or just be safer as to where you surf).