- cross-posted to:
- programming
- [email protected]
- [email protected]
- cross-posted to:
- programming
- [email protected]
- [email protected]
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.
You must log in or register to comment.
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 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.
Lol true thats a pretty small app
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
Hmmmm. Maybe this is why Debian pushed a curl update today even though it was also upgraded in 12.2 four days ago
expired
