▲ 64 ▼ Big not-yet-disclosed PHP vulnerability (www.php.net) submitted 21 hours ago by chicken@lemmy.dbzer0.com to c/cybersecurity@sh.itjust.works 8 comments fedilink hide all child comments
[–] GottaHaveFaith@fedia.io 2 points 19 hours ago (5 children) POC at https://jackalsyn.com/posts/php-up-2026.html permalink fedilink source hideshow 5 child comments replies: [–] CorrectAlias@piefed.blahaj.zone 2 points 19 hours ago (4 children) God I hate all of the slopisms in this POC site. It makes it so annoying to read, so much filler. permalink fedilink source parent hideshow 4 child comments replies: [–] GottaHaveFaith@fedia.io 1 point 18 hours ago (3 children) Yeah but it has the python sources, you can skip the haxx0r l33t permalink fedilink source parent hideshow 3 child comments replies: [–] CorrectAlias@piefed.blahaj.zone 3 points 18 hours ago* (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] GottaHaveFaith@fedia.io 5 points 17 hours ago 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. permalink fedilink source parent [–] vk6flab@lemmy.radio 1 point 16 hours ago 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 permalink fedilink source parent
[–] CorrectAlias@piefed.blahaj.zone 2 points 19 hours ago (4 children) God I hate all of the slopisms in this POC site. It makes it so annoying to read, so much filler. permalink fedilink source parent hideshow 4 child comments replies: [–] GottaHaveFaith@fedia.io 1 point 18 hours ago (3 children) Yeah but it has the python sources, you can skip the haxx0r l33t permalink fedilink source parent hideshow 3 child comments replies: [–] CorrectAlias@piefed.blahaj.zone 3 points 18 hours ago* (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] GottaHaveFaith@fedia.io 5 points 17 hours ago 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. permalink fedilink source parent [–] vk6flab@lemmy.radio 1 point 16 hours ago 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 permalink fedilink source parent
[–] GottaHaveFaith@fedia.io 1 point 18 hours ago (3 children) Yeah but it has the python sources, you can skip the haxx0r l33t permalink fedilink source parent hideshow 3 child comments replies: [–] CorrectAlias@piefed.blahaj.zone 3 points 18 hours ago* (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] GottaHaveFaith@fedia.io 5 points 17 hours ago 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. permalink fedilink source parent [–] vk6flab@lemmy.radio 1 point 16 hours ago 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 permalink fedilink source parent
[–] CorrectAlias@piefed.blahaj.zone 3 points 18 hours ago* (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] GottaHaveFaith@fedia.io 5 points 17 hours ago 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. permalink fedilink source parent [–] vk6flab@lemmy.radio 1 point 16 hours ago 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 permalink fedilink source parent
[–] GottaHaveFaith@fedia.io 5 points 17 hours ago 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. permalink fedilink source parent
[–] vk6flab@lemmy.radio 1 point 16 hours ago 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 permalink fedilink source parent