← Back to context Comment by gnabgib 1 day ago > These vulnerabilities could affect all PHP versions from PHP 5 onwardshttps://news.ycombinator.com/item?id=50167754) 4 comments gnabgib Reply Operyl 1 day ago I love the "affects PHP... 6" given we never had an official 6 release haha. gnabgib 1 day ago Yeah.. their text (unedited).. Maybe they meant 5.6? Only 8.x is "supported" currently, though. I wonder how 3&4 avoided it :) cesarb 1 day ago > I wonder how 3&4 avoided it :)Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release. Perz1val 17 hours ago A: I'm writing a post, what versionsB: "5.6, 7, 8“A: fixes a "typo" ok so "5, 6, 7, 8"
Operyl 1 day ago I love the "affects PHP... 6" given we never had an official 6 release haha. gnabgib 1 day ago Yeah.. their text (unedited).. Maybe they meant 5.6? Only 8.x is "supported" currently, though. I wonder how 3&4 avoided it :) cesarb 1 day ago > I wonder how 3&4 avoided it :)Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release. Perz1val 17 hours ago A: I'm writing a post, what versionsB: "5.6, 7, 8“A: fixes a "typo" ok so "5, 6, 7, 8"
gnabgib 1 day ago Yeah.. their text (unedited).. Maybe they meant 5.6? Only 8.x is "supported" currently, though. I wonder how 3&4 avoided it :) cesarb 1 day ago > I wonder how 3&4 avoided it :)Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release. Perz1val 17 hours ago A: I'm writing a post, what versionsB: "5.6, 7, 8“A: fixes a "typo" ok so "5, 6, 7, 8"
cesarb 1 day ago > I wonder how 3&4 avoided it :)Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release.
Perz1val 17 hours ago A: I'm writing a post, what versionsB: "5.6, 7, 8“A: fixes a "typo" ok so "5, 6, 7, 8"
I love the "affects PHP... 6" given we never had an official 6 release haha.
Yeah.. their text (unedited).. Maybe they meant 5.6? Only 8.x is "supported" currently, though. I wonder how 3&4 avoided it :)
> I wonder how 3&4 avoided it :)
Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release.
A: I'm writing a post, what versions
B: "5.6, 7, 8“
A: fixes a "typo" ok so "5, 6, 7, 8"