From the little info one can see here, it looks like this is a PHP script causing a memory corruption. So you probably need to be able to run PHP code to exploit it.

That's... not a particularly unusual issue. PHP has a large codebase, releases with plenty of fixed crashes come out regularly. It becomes critical if there's a remote path to exploitation.

I see no indication that this is a "critical" PHP flaw. And the Reply from the person who found it seems to confirm that. ("I keep getting asked about mitigations, here's the mitigation: don't worry about it kitten")

There is literally no info on how this is triggered. From the info this could range anywhere from total non issue to zOMG. Given how keyed up everyone is, i lean towards the former.

honestly, i would just wait for php announcement and assume its no big deal until then.

Oh, it's going to be one of those weeks.

Got really triggered... By the font.

PHP is having a really bad day today

I mean it the first time [0], PHP is done.

[0] https://news.ycombinator.com/item?id=50181423

undefined

undefined

[dead]