I believe Microsoft has already created a fix for this. KB2961887