It's understandable, really. 100% reliable arbitrary code execution exploits are bad enough all by themselves. The nature of the exploit in question - which many would consider to be a Freshman error that was allowed to stand for an embarrassingly long time - makes it even more galling.