In association with the release of curl 8.4.0, we publish a security advisory and all the details for CVE-2023-38545. This problem is the worst security problem found in curl in a long time. We set it to severity HIGH.

While the advisory contains all the necessary details. I figured I would use a few additional words and expand the explanations for anyone who cares to understand how this flaw works and how it happened.

top 6 comments

sorted by: hot top controversial new old

[–] onlinepersona@programming.dev 8 points 11 months ago (2 children)

He brings up the "just rewrite in rust" argument. Curious as I am, I had a look and only found a single project that actually tried it https://github.com/TogarashiPepper/curl

It didn't get very far.

[–] the_ocs@lemmy.world 6 points 11 months ago

The argument for rust is memory safety, which allows you to avoid these very common, often serious, issues.

It's an argument that goes far beyond curl, and some random curl clone written in rust.

[–] Pantherina@feddit.de -1 points 11 months ago

Lol true thats a pretty small app

[–] makeasnek@lemmy.ml 5 points 11 months ago

These things happen, best you can do is fix them when they do and accept responsibility. Cheers to the devs. Memory-safe languages are the future

[–] macallik@kbin.social 3 points 11 months ago (1 children)

Hmmmm. Maybe this is why Debian pushed a curl update today even though it was also upgraded in 12.2 four days ago

[–] 7heo@lemmy.ml 4 points 11 months ago* (last edited 11 months ago)

expired