3 ms·
prior to now, no. if you're referring to the 2003 exploit, well, i was 14 when that happened. as i previously mentioned, an exploit from allocating data based
by foxhill 12y ago
prior to now, no. if you're referring to the 2003 exploit, well, i was 14 when that happened.
as i previously mentioned, an exploit from allocating data based on unvalidated untrusted user input is.. practically a tautology.
- tedunangst 12y agoYou appear to be vehemently denying the existence of a class of bugs that has plagued programs for longer than you've been programming. Perhaps reconsider how much experience you actually have.
- foxhill 12y agoeven though, prior to this thread, i'd never heard of 2 bugs exploiting this issue, i'm not denying their existence at all. only their likelihood of occurring. 10 years since i started programming, 7 of which i consider good enough to be "experience", is the answer to your statement. less than many here, but i'm certainly not a novice.
- scott_s 12y ago"Likelihood" is the wrong way to think about security vulnerabilities. Once an exploit such as this is known to be possible, attackers can contrive scenarios to exploit it.