Has anyone read this yet? Apparently it’s quite serious and I’ve managed it replicate it on my local machine.
Yeah, I popped up a couple of tweets (here, [URL=“http://twitter.com/AnthonySterling/status/22225202964340736”]here and [URL=“http://twitter.com/AnthonySterling/status/22262184604082176”]here) about it this morning. The [URL=“http://bugs.php.net/bug.php?id=53632”]bug report seems to indicate 64bit systems are fine though, will confirm tonight.
As expressed in this reply to Rasmus Lerdorf’s [URL=“http://twitter.com/rasmus/status/22226334654664705”]tweet to me, I do worry how shared hosting folk will be affected by this.
It crashed my Windows dev box (admittedly my fault) when I was testing this bug as it completely consumed the CPU, I had to fill a nice report in for that to Head Office!
This is the code I used:
<?php #?boom=2.2250738585072011e-308 echo isset($_GET['boom']) ? (float)$_GET['boom'] : 0 ; /* Hangs */
The ExploringBinary post is an excellent overview and well worth a read, including the comments.
Well, apparently the bug has been found and it is possible to fix the bug itself and to patch your own servers to stop this from happening, but sadly this news won’t reach the vast majority of developers and there may be a lot of websites out there that could be targeted if they’re handling floating-point numbers in their form fields as GETs.
Im running om Windows Vista Business 64bit, and managed to crash my XAMPP running PHP Version 5.3.1
How it crashed:
in the code I have this check:
I assume that’s because you’re running a 32bit version of Apache.
That might be the case… it is just a simple XAMPP install.
All is well here. 5.3.3(cli), 64bit, LAMP.
We have slapped together a quick workaround that prevents malicious DoS attacks with this mechanism.
Code can be found here: