PHP multiple imap functions safemode and open_basedir restriction bypass
| php-imap-restriction-bypass (24964) |  Medium Risk |
Description:
PHP could allow a remote attacker to bypass security restrictions when the safemode and open_basedir restrictions are enabled. A remote attacker could exploit this vulnerability by passing extra commands to the imap_open, imap_body, imap_list, imap_createmailbox, imap_deletemailbox or imap_renamemailbox functions which would allow the attacker to view and possibly modify arbitrary files and directories on Web servers that are running a vulnerable version of PHP.
*CVSS:
| Base Score: | 5.6 |
| Access Vector: | Remote |
| Access Complexity: | High |
| Authentication: | Not Required |
| Confidentiality Impact: | Partial |
| Integrity Impact: | Partial |
| Availability Impact: | Partial |
| Temporal Score: | 4.1 |
| Exploitability: | Unproven |
| Remediation Level: | Official-Fix |
| Report Confidence: | Confirmed |
Consequences:
Bypass Security
Remedy:
Upgrade to the latest version of PHP (4.4.4 or later) or (5.1.5 or later), available from The PHP Group Web site. See References.
References:
- BugTraq Mailing List, Tue Feb 28 2006 - 12:50:35 CST: (PHP) imap functions bypass safemode and open_basedir restrictions.
- The PHP Group Web site: PHP 5.1.5 Release Announcement.
- The PHP Group Web site: PHP 4.4.4 Release Announcement.
- The PHP Group Web site: PHP: Downloads.
- CVE-2006-1017: The c-client library 2000, 2001, or 2004 for PHP before 4.4.4 and 5.x before 5.1.5 do not check the (1) safe_mode or (2) open_basedir functions, and when used in applications that accept user-controlled input for the mailbox argument to the imap_open function, allow remote attackers to obtain access to an IMAP stream data structure and conduct unauthorized IMAP actions.
- CVE-2006-7204: The imap_body function in PHP before 4.4.4 does not implement safemode or open_basedir checks, which allows local users to read arbitrary files or list arbitrary directory contents.
- MDKSA-2006:122: Updated php packages fix multiple vulnerabilities
- OSVDB ID: 23535: PHP imap_open() Function open_basedir/safe_mode Bypass
- OSVDB ID: 28005: PHP imap_body() Function open_basedir/safe_mode Bypass
- SA18694: PHP "mb_send_mail()" and IMAP Functions Security Bypass
- SA21546: PHP Multiple Vulnerabilities
- VUPEN/ADV-2006-0772: PHP Multiple Functions Security Bypass and File Manipulation Issues
Platforms Affected:
- MandrakeSoft Mandrake Linux 2006 X86_64
- MandrakeSoft Mandrake Linux 2006
- MandrakeSoft Mandrake Linux LE2005
- MandrakeSoft Mandrake Linux LE2005 X86_64
- MandrakeSoft Mandrake Linux Corporate Server 3.0 X86_64
- MandrakeSoft Mandrake Linux Corporate Server 3.0
- MandrakeSoft Mandrake Multi Network Firewall 2.0
- PHP PHP 4.0
- PHP PHP 5.0.0
Reported:
Feb 28, 2006
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
* According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
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 IBM be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.