this post was submitted on 04 Oct 2023
62 points (97.0% liked)

Programming

18018 readers
18 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

Posted on twitter by Curl author Daniel Stenberg - https://nitter.cz/bagder/status/1709103920914526525

We are cutting the release cycle short and will release curl 8.4.0 on October 11, including a fix for a severity HIGH CVE. Buckle up.

... But this time actually the worst security problem found in curl in a long time

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545

all 9 comments
sorted by: hot top controversial new old
[–] Black616Angel@feddit.de 13 points 1 year ago (2 children)

Who also guesses buffer overflow or use-after-free?

[–] ultratiem@lemmy.ca 11 points 1 year ago (1 children)

Buffer overflows are like Lupus in House M.D.

[–] __init__@programming.dev 5 points 1 year ago

It’s not overflow. It’s never overflow.

[–] MajorHavoc@lemmy.world 10 points 1 year ago* (last edited 1 year ago)

I want to thank the curl developers for taking security issues seriously to keep me safe.

Now I'm going to go pipe another curl script output directly into a sudo bash command. /s

We need a version of /s for "I'm not actually doing this right now... but we know I still will..."