BLUE
Profile banner
🍂aksfjh👖
@db-user.bsky.social
more aks, but now with more dogs. Radical liberal. Hot dogs are not sandwiches. Pro dumpling account aksfjh on discord he/them I use databases, not all of them are good. i've won awards, no you can't see them
720 followers431 following18.6k posts
db-user.bsky.social

this is the main reply from a dev gives some context and hints that they are not seeing nor hearing about this exploited in the wild there doesn't appear to be a public exploit available either, but I'll admit I just did a cursory search

I set the date to

• allow us a few days for more deliberating on the vulnerability, to really think it through, write the advisory, understand it proper. Rinse and repeat.
• give "distro people" a few days to prepare patched updates
• allow a few days for the project (and me) to line up things to prepare for the new release
• we can spread the word about the pending release and the main reason for it in the mean time
• the release needs to work with my personal schedule and Wednesdays are our standard release days

Sure, there is a minuscule risk that someone can find this (again) before we ship the patch, but this issue has stayed undetected for years for a reason. I think taking a few days to make sure we do a solid release is worth this risk.
1

DBretr0.id

psa to anyone exploit-searching: there will almost certainly be fake exploits that pwn you if you run them

1
Profile banner
🍂aksfjh👖
@db-user.bsky.social
more aks, but now with more dogs. Radical liberal. Hot dogs are not sandwiches. Pro dumpling account aksfjh on discord he/them I use databases, not all of them are good. i've won awards, no you can't see them
720 followers431 following18.6k posts