Think about it for a second... It makes perfect sense.
It looks like an "innocent" bug, yet gives full access to the system. Perfect deniability for both MS and whatever shady organization that's behind this (FBI, CIA, NSA, Homeland Security, whatever). Also, there's been SO MANY of them too. It was YEARS ago that MS said they were putting down the foot on these buffer overflows (while XP was still under development even!), still they keep popping up. You may remember MS even halted their work while they went through code to sniff out buffer overflows.
Maybe it ISN'T so accidental...
Or maybe MS is just a bunch of maroons who couldn't code securely if their life depended on it, what do I know. Anyway, it's fun to conspire and think up theories involving such.
It looks like an "innocent" bug, yet gives full access to the system. Perfect deniability for both MS and whatever shady organization that's behind this (FBI, CIA, NSA, Homeland Security, whatever). Also, there's been SO MANY of them too. It was YEARS ago that MS said they were putting down the foot on these buffer overflows (while XP was still under development even!), still they keep popping up. You may remember MS even halted their work while they went through code to sniff out buffer overflows.
Maybe it ISN'T so accidental...
Or maybe MS is just a bunch of maroons who couldn't code securely if their life depended on it, what do I know. Anyway, it's fun to conspire and think up theories involving such.