It took Adobe 3 months to issue a patch for this to begin with, are we going to have to wait another 3 months?
In the meantime Didier Stevens, who originally found the problem has done some research and found why this is taking place. Apparently, Adobe has used a blacklist type method to allow or deny the Launch action.
Stevens has provided a workaround in his blog, allowing users to go into the registry and add to the "blacklist" of non-allowed commands. Check out his post below for more info on how to do this from the Windows Registry. For those not comfortable fooling around in there, let's hope Adobe is quicker to get a better working patch out this time.
