CVE-2004-1064

• BID:11964
• URL:http://www.securityfocus.com/bid/11964
• BUGTRAQ:20041215 Advisory 01/2004: Multiple vulnerabilities in PHP 4/5
• URL:http://www.securityfocus.com/archive/1/384545
• CONECTIVA:CLA-2005:915
• URL:http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000915
• CONFIRM:http://www.php.net/release_4_3_10.php
• GENTOO:GLSA-200412-14
• URL:http://www.gentoo.org/security/en/glsa/glsa-200412-14.xml
• HP:HPSBMA01212
• URL:http://www.securityfocus.com/advisories/9028
• MANDRAKE:MDKSA-2004:151
• URL:http://www.mandriva.com/security/advisories?name=MDKSA-2004:151
• MANDRAKE:MDKSA-2005:072
• URL:http://www.mandriva.com/security/advisories?name=MDKSA-2005:072
• MISC:http://www.hardened-php.net/advisories/012004.txt
• UBUNTU:USN-99-1
• URL:https://www.ubuntu.com/usn/usn-99-1/
• UBUNTU:USN-99-2
• URL:https://www.ubuntu.com/usn/usn-99-2/
• XF:php-realpath-safemode-bypass(18512)
• URL:https://exchange.xforce.ibmcloud.com/vulnerabilities/18512

 Christey> There is active disagreement regarding whether this satisfies the
   criteria for inclusion in CVE, because the attack vectors require
   function parameters that are typically controlled only by the
   application developer, not an external attacker.  This would mean that
   only the PHP application owner could exploit it.
   
   Since various PHP functions already allow the application owner to
   execute commands, no additional privileges would be gained by
   exploiting such a bug.  However, if safe_mode is enabled in PHP, then
   the PHP functions related to execution are restricted
   (e.g. shell_exec()).  Thus, exploitation may allow the PHP application
   owner to execute code *despite* the configured restrictions imposed by
   safe mode, which then qualifies this as a vulnerability.