The rumor began when
popinjay expert Steve Gibson examined an unofficial patch issued by Ilfak Guilfanov, and,
due to his lack of security experience, observed behavior that he could not explain by means other than a Microsoft conspiracy.
...
Gibson could not imagine why WMF rendering should need the SetAbortProc API, since,
as he mistakenly believed, WMF outputs to a screen, not a printer. In fact, it can output to a printer as well. But following
Gibson's erroneous assumption, the question arose: what would be the point of polling the process and allowing the user, or application, to cancel it?
Having exhausted his imagination on that score, he concluded that there's no good reason for SetAbortProc to be involved in handling metafiles.
The more logical explanation, Gibson reckoned, was that someone at Microsoft had deliberately back-doored Windows with this peculiar little stuff-up. And besides, the idea of compromising a computer with an image file
seemed quite cloak-and-dagger, adding to the supposed "mystery."
...
Here Gibson takes his preferred route to getting the ink that he craves: technobabble and innuendo. He can't prove anything (technically, he hasn't got the chops), so he lurks in the gray area between fact and fiction, and generates torrents of fear, uncertainty, and doubt.
The FUD Olympics
Gibson has a bad track record: a history of latching onto arcane issues that he doesn't fully understand and can never prove, and converting his limited understanding into fodder for the next internet melt-down.
...
The WMF backdoor very much in keeping with
Gibson's history of getting security matters a bit wrong, filling the gaps in his understanding with technobabble, and hyping the actual matter out of all reasonable proportion in his neverending quest of ink.
And here, much as we regret it, we've given him even more ink. We can only hope that it dispels the ridiculous rumor that Gibson has propagated, and thus will do more good than harm.