←back to thread

354 points dgl | 1 comments | | HN request time: 1.044s | source
Show context
acheong08 ◴[] No.44504558[source]
Reproduced the issue after a bit: https://github.com/acheong08/CVE-2025-48384 Then immediately went to update my git version. Still not up on Arch yet. Will refrain from pulling anything but I bet it'll take quite a while for most people to upgrade. Putting it in any reasonable popular repo where there are perhaps automated pulls will be interesting.
replies(2): >>44504609 #>>44509460 #
orblivion ◴[] No.44504609[source]
So this was disclosed before patching? With all of the alarming "here's how we can pwn your machine" posts turning out to be months after the fact, I figured by now that these blog posts all happen after all the distros have long patched it.

It seems like it would be appropriate to make it clear "this is important now" vs "don't worry you probably already patched this" in the headline to save our time for those who aren't just reading these posts out of interest.

replies(1): >>44504733 #
acheong08 ◴[] No.44504733[source]
Commits fixing the bug date back around 3 or 4 weeks. The patched release came 3 weeks ago. Perhaps some parties weren't informed that it's security critical (Homebrew, Arch, etc) and are now scrambling
replies(3): >>44504804 #>>44505793 #>>44505977 #
1. orblivion ◴[] No.44505793[source]
Am I reading this wrong? As of this writing it all says "vulnerable".

https://security-tracker.debian.org/tracker/CVE-2025-48384