4 ms·
This doesn't look intentional at all, because this is basically like how 90% of memory disclosure bugs look
by saagarjha 3y ago
This doesn't look intentional at all, because this is basically like how 90% of memory disclosure bugs look
- somenameforme 3y agoAbsolutely. And that's the point I'm making here. It is essentially impossible to discern between an exploit injected due to malice, and one injected due to incompetence. It reminds one of the CIA's 'simple sabotage field manual' in this regard. [1] Many of the suggestions look basically like a synopses of Dilbert sketches, written about 50 years before Dilbert, because they all happen, completely naturally, at essentially any organization. The manual itself even refers to its suggestions as "purposeful stupidity." You're basically exploiting Hanlon's Razor. [1] - https://www.openculture.com/2015/12/simple-sabotage-field-manual.html https://www.openculture.com/2015/12/simple-sabotage-field-ma...
- andix 3y agoNobody can tell if they are intentional or accidental.
- foldr 3y agoI suppose the point is that even though any given instance of an error like this is overwhelmingly likely to be an innocent mistake, there is some significant probability that one or two such instances were introduced deliberately with plausible deniability. Although this amounts to little more than the claim that "sneaky people might be doing shady things, for all we know", which is true in most walks of life.