Technology

60044 readers

2852 users here now

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

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

170

A twenty-five years old curl bug (daniel.haxx.se)

submitted 1 week ago by 0x0 to c/[email protected]

7 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 7 comments

sorted by: hot top controversial new old

[–] [email protected] 28 points 1 week ago (1 children)

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

[–] [email protected] 3 points 1 week ago

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

[–] [email protected] 8 points 1 week 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

[–] [email protected] 4 points 1 week ago

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

[–] [email protected] 4 points 1 week ago (1 children)

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

[–] [email protected] 3 points 1 week ago (1 children)

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

[–] [email protected] 7 points 1 week ago

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