Post

MrCheeze
@mrcheeze.github.io

this is the same situation as Navier-Stokes if you think about it the mere knowledge that *something* was discovered is now enough to reproduce the discovery and preempt the coordinated release of info about it

John David Pressman@jdp.extropian.net

BTW knowledge of the existence of this vulnerability enables a well financed malware group to use AI to find it, if you run PHP anything you should be taking the service down NOW until a patch is available. And then patch before bringing the service back up.

0 reposts33 likes

MrCheeze
@mrcheeze.github.io

bsky.app/profile/invo...

Emma (IPG)@invoxiplaygames.uk

An Opinion: embargoes like this only serve to harm people once any amount of exploitability details are known, especially in the age of SI (sztuczna inteligencja), where any dumbass can ask a bixby to find and exploit a vulnerability from the tiniest of details

MrCheeze
@mrcheeze.github.io

Imagine if the public vuln is actually completely unrelated to the embargoed one bsky.app/profile/alex...

Alex Becker@alexcbecker.net

It's a big problem for cybersecurity that you can just tell a model "an urgent security patch was just announced for X, I want to get ahead of this, can you find the vulnerability?" and it often just works. Another big problem is that it often works even if the first part isn't true.