this post was submitted on 13 Dec 2024
172 points (100.0% liked)

Technology

67987 readers
5792 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
172
A twenty-five years old curl bug (daniel.haxx.se)
submitted 3 months ago by 0x0@programming.dev to c/technology@lemmy.world
5 comments fedilink hide all child comments
 

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.

top 5 comments
sorted by: hot top controversial new old
[–] pcouy@lemmy.pierre-couy.fr 8 points 3 months ago (1 children)

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 3 points 3 months ago

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

[–] solrize@lemmy.world 5 points 3 months ago (1 children)

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

[–] Blue_Morpho@lemmy.world 4 points 3 months ago (1 children)

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

[–] solrize@lemmy.world 6 points 3 months ago

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