Submitted 3 hours ago by 
INeedMana@piefed.zip to selfhosted@lemmy.world
https://eliastaylor.com/noexploit/
from https://mastodon.social/@CuratedHackerNews/117481600704689796
Last time I touched php it was ~20 years ago and maybe for a month. Could someone with actual php understanding weigh in?
Somehow, somewhere between the lines, my understanding was that there have been observances of the vuln being used in the wild before the 14 UTC. And that wasn’t from reading news sites
The PHP vulnerabilities (yes there is more than one) are relatively easy to exploit if you can fiddle with what requests your server receives (easy).
The DNS exploit requires someone to figure out how to man-in-the-middle your connection. While that is trivial for governments, it is much less likely to be done by purely bad actors, simply for how visible the problem is.
Both are big problems, but only one of them is continually exploitable, as the DNS issues have been largely resolved even before the very public disclosure.
What do you mean “DNS exploit”? Neither 109618 nor 109619 mention dns in the exploit path…
stopforgettingit@lemmy.world 3 hours ago
The bug is real, its exploitable but only if the server also has a very specific vulnerability in order for php to be exploited. Which kind of makes it a non exploit. And the author is backing that up by point out the php runs about 70% of the web and the exploit has been out for over 10 hours (when this was written), if this was a real “we are very fucked” bug, we would be hearing about all the fall out from this already and we have heard nothing.
The (quite funny actually) take away here is that the “smoking gun” demos that prove this exploit show that the server vulnerability was specifically mimicked before the exploit test was run.