A twenty-five years old curl bug (daniel.haxx.se)
from 0x0@programming.dev to technology@lemmy.world on 13 Dec 09:25
https://programming.dev/post/22791770

I like the clarification:

Let me also touch this subject while talking security problems. This bug, the oldest so far in curl history, was a plain logic error and would not have been avoided had we used another language than C.

Otherwise, about 40% of all security problems in curl can be blamed on us using C instead of a memory-safe language. 50% of the high/critical severity ones.

Almost all of those C mistakes were done before there even existed a viable alternative language – if that even exists now.

#technology

threaded - newest

solrize@lemmy.world on 13 Dec 10:38 next collapse

I wonder whether some careful specifications and model checking could have found this.

Blue_Morpho@lemmy.world on 13 Dec 13:10 collapse

As the article says, the problem was the logic. They had thousands of hours of model checking.

solrize@lemmy.world on 13 Dec 15:46 collapse

They had 1000s of hours of fuzz testing. Model checking means something different.

Kolanaki@yiffit.net on 13 Dec 10:40 next collapse

I didn’t look at the community and was expecting to see a decade old woodlouse.

pastermil@sh.itjust.works on 13 Dec 11:24 collapse

Technically, it exists, just in pieces. You probably have ingested some of those pieces.

pcouy@lemmy.pierre-couy.fr on 13 Dec 18:34 collapse

When looking at the CVE itself, it seems like a bug that only gets triggered on a very specific corner case that neither the client or website alone can trigger.

Of course, it’s good that it gets reported and fixed, but I’m pretty sure these kind of bugs can only get caught by people randomly stumbling on them

gwilikers@lemmy.ml on 13 Dec 20:14 collapse

Someone earned a tidy 540 bucks stumbling onto this one. Not bad.