Weeks?
ok, im fairly sure this issue was made public at a blackhat security conference (without informing microsoft) on Fri 17th, work arounds and alternative protection was provided by MS on 20th and a full patch by the 28th,
i think they handled it superbly for once