3 ms·
I recommend looking at the top comment in https://news.ycombinator.com/item?id=13966241 https://news.ycombinator.com/item?id=13966241. Stenberg said, and may b
by btilly 10y ago
I recommend looking at the top comment in https://news.ycombinator.com/item?id=13966241 https://news.ycombinator.com/item?id=13966241.
Stenberg said, and may believe, that C is not the source of most of curl's security problems. But examining counts of security vulnerabilities, it definitely is.
- falcolas 10y agoIt's worth noting that those vulnerabilities appear to be from a security review; 10 of them were all posted on the same day (11/2/16). So the reality is that most of these didn't have practical impacts or attacks; they just needed to be fixed. Putting that batch of 10 CVEs aside, the number of memory related bugs is quite small. In the greater scope of things, ~60 CVEs over the course of 17 years is pretty small.
- lawnchair_larry 10y agoI don't understand your logic. The vulnerabilities were there. It doesn't matter who found them or when.
- thomastjeffery 10y ago> It doesn't matter who found them or when. It does matter. No vulnerability can be used without knowledge of that vulnerability, therefore it matters who found it (did they publish or abuse the vulnerability?) and when (was it published shortly after the first discovery?).
- pseudalopex 10y agoSome attacks don't get published, and the author specifically argues against comparing bug counts.
- lvh 10y agoI disagree that you can infer anything about impact because they were found in an audit. That just means they weren't publicly known, it does not mean they weren't known to someone.