
Originally Posted by
javamorg
Quality Assurance testing is an essential requirement. The issue described is expected to be addressed by the addition of a php.ini directive ("max_file_uploads") in the upcoming PHP version 5.2.12 upon its final release; related to the upcoming version, we have completed initial testing of PHP 5.2.12RC3 per internal case ID #35835.

Originally Posted by
Datcrack
Just came to say the same. We need 5.3.1 right away. Or perhaps if there's a patch for 5.2.x it would be sufficient. But cPanel needs to act now.
Regarding patching the existing PHP version 5.2.11 this is being actively tracked in the following internal case ID: #35955

Originally Posted by
yayyo
+1 for option to upgrade to PHP 5.3.1 - thanks.
Borken scripts have gotta be a better choice than "in the wild" DOS/exploit.
Please note that at any time you may apply preventative measures, such as one or both of the following steps:
1.) Disable file uploads via php.ini setting:
2.) If needing to allow file uploads, then you could use Suhosin that is available in EasyApache and enable enforcement via php.ini setting:
Code:
suhosin.simulation = Off
Optionally, you may customize the Suhosin php.ini setting "suhosin.upload.max_uploads" that defaults to 25, which is similar to the PHP 5.3.1 default of 20 for "max_file_uploads":
Code:
suhosin.upload.max_uploads = 25
Related reference: CVE - CVE-2009-4017 (under review)