PHP multiple COM objects security bypass
| php-com-security-bypass (37368) |  Medium Risk |
Description:
PHP could allow a remote attacker to bypass the safe_mode and disable_function security restrictions, caused by improper handling of COM objects. By uploading a malicious script to the server, an attacker could exploit this vulnerability to execute arbitrary commands on the system.
Platforms Affected:
- PHP, PHP 5.0.0
- PHP, PHP 5.0.0 RC1
- PHP, PHP 5.0.0 RC3
- PHP, PHP 5.0.0 RC2
- PHP, PHP 5.0.0 Beta2
- PHP, PHP 5.0.0 Beta4
- PHP, PHP 5.0.0 Beta3
- PHP, PHP 5.0.0 Beta1
- PHP, PHP 5.0.1
- PHP, PHP 5.0.2
- PHP, PHP 5.0.3
- PHP, PHP 5.0.4
- PHP, PHP 5.0.5
- PHP, PHP 5.1.0
- PHP, PHP 5.1.1
- PHP, PHP 5.1.2
- PHP, PHP 5.1.3
- PHP, PHP 5.1.4
- PHP, PHP 5.1.5
- PHP, PHP 5.1.6
- PHP, PHP 5.2.0
- PHP, PHP 5.2.1
- PHP, PHP 5.2.2
- PHP, PHP 5.2.3
- PHP, PHP 5.2.4
Remedy:
No remedy available as of July 4, 2009.
Consequences:
Bypass Security
References:
- The PHP Group Web site, PHP: Hypertext Preprocessor at http://www.php.net/.
- CVE-2007-5653: The Component Object Model (COM) functions in PHP 5.x on Windows do not follow safe_mode and disable_functions restrictions, which allows context-dependent attackers to bypass intended limitations, as demonstrated by executing objects with the kill bit set in the corresponding ActiveX control Compatibility Flags, executing programs via a function in compatUI.dll, invoking wscript.shell via wscript.exe, invoking Scripting.FileSystemObject via wshom.ocx, and adding users via a function in shgina.dll, related to the com_load_typelib function.
- SA27280: PHP COM Objects Security Bypass
- VUPEN/ADV-2007-3590: PHP for Windows COM Objects Handling Security Bypass Vulnerability
Reported:
Oct 22, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net