ID: 17415 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Bogus Bug Type: *Directory/Filesystem functions Operating System: Windows 2000 IIS 5 SP2 PHP Version: 4.2.1
Previous Comments: ------------------------------------------------------------------------ [2002-05-24 14:59:08] [EMAIL PROTECTED] whilst there is a bug here in that exec is pretty useless on win2k, giving r/w permissions on cmd.exe isn't a bug -- this is the only way really you can do filesystem stuff on windows. this is the same as php on *nix, it needs access to a standard shell to perform file functions. none of the filesystem functions are overly safe, (it probably would negate the point of them if they were) but if you were to set permissions aggressively, you should be able to workaround this. as for who handles accounts for which apps run under, that'd be Bill Gates, and his IIS team -- IUSR-<task/machine name> accounts are designed to be unprivileged accounts that can run stuff (sounds wierd, huh?) under the guise of internet programs. PHP is a powerful scripting language -- and if you really want to be safe, move to *nix, chroot, and restrict access to functions. ------------------------------------------------------------------------ [2002-05-24 14:25:59] [EMAIL PROTECTED] One cannot utilize the exec() funtion without granting read/execute rights to the IUSR-machinename account on cmd.exe. This is a major security flaw on windows systems. Almost all of the exploits on IIS systems stem from allowing the IUSR account to have read/execute permissions on cmd.exe. So, with that said, the exec() function is unusable on IIS. I'm new to PHP and I don't know who handles the decisions for which accounts an app runs under, but whoever you are you need to change this yesterday to protect the users of PHP on windows. Peace. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17415&edit=1
