Except that the creator of the slop PoC broke embargo and the mitigations inside are not enough according to a core PHP dev. So whoever created this site just put millions of sites at risk of this exploitation. See: https://mastodon.social/@Girgias@phpc.social/117476477662524828
Whatever you like it or not, we are in the LLM age, if pointing Claude to a CVE is enough to have a POC, embargoes are not going to do anything anymore.
At this point that’s not unexpected. Given the proliferation of tools generally, if not freely, available, it would be naive to think that the published PoC was the only one in existence.
As a result, the curl project has just changed their CVE policy to publish all with a severity less than HIGH, starting 26 October.
God I hate all of the slopisms in this POC site. It makes it so annoying to read, so much filler.
Yeah but it has the python sources, you can skip the haxx0r l33t
Except that the creator of the slop PoC broke embargo and the mitigations inside are not enough according to a core PHP dev. So whoever created this site just put millions of sites at risk of this exploitation. See: https://mastodon.social/@Girgias@phpc.social/117476477662524828
Whatever you like it or not, we are in the LLM age, if pointing Claude to a CVE is enough to have a POC, embargoes are not going to do anything anymore.
At this point that’s not unexpected. Given the proliferation of tools generally, if not freely, available, it would be naive to think that the published PoC was the only one in existence.
As a result, the curl project has just changed their CVE policy to publish all with a severity less than HIGH, starting 26 October.
See:
https://github.com/curl/curl/discussions/23458