PHP is a general purpose scripting language widely used in World Wide Web (WWW) pages and applications.
Vulnerable versions of PHP were found to have an integer overflow condition in the PHP memory handling routines. A remote malicious user could possibly execute arbitrary code as the apache user on a host running PHP if a script can allocate memory in relation to untrusted user data. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-4812 to this issue.
PHP's sscanf() function was found to contain a buffer overflow condition. Using sscanf() with positional arguments in the format string, a malicious remote user could possibly execute arbitrary code as the apache user using carefully constructed requests. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-4020 to this issue.
Two integer overflow issues were found in vulnerable versions of PHP running on 64-bit systems. These issues could lead to either a heap overflow or possible Denial of Service (DoS) conditions. Avaya system products are not affected by these issues as they are 32-bit systems. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2006-4482 and CVE-2006-4486 to these issues.
The gd extension for vulnerable versions of PHP was found to contain a buffer overflow flaw. Using a specially crafted GIF image file, a remote malicious user could possibly cause a heap overflow if a script processed GIF images via the gd extension from untrusted sources. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-4484 to this issue.
The stripos() function was found to contain a buffer overread issue in vulnerable versions of PHP. Scripts utilizing stripos() and allowing untrusted remote user data could possibly cause a Denial of Service (DoS) condition as PHP might read beyond the end of the buffer. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-4485 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya S87XX/S8500/S8300||CM 2.2 Load 126 and prior||Low||Upgrade to CM 2.2 Load 127 or later in the CM 2.2 series or CM 3.1 or later in the CM 3.x series to remove PHP.|
|Avaya Messaging Storage Server||MSS 3.0||Medium||Update to MSS 3.1 or later.|
|Avaya CCS/SES||SES 3.1.1||Medium||Update to SES 5.0 or later.|
For all system products which use vulnerable versions of PHP, Avaya recommends that customers restrict local and network access to the server. This restriction should be enforced through the use of physical security, firewalls, ACLs, VPNs, and other generally-accepted networking practices until such time as an update becomes available and can be installed.
Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.
In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendors guidance:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|CVLAN||All||None||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application. The CVLAN application does not require the software described in this advisory.|
|Avaya Integrated Management Suite(IMS)||All||None||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application. The IMS application does not require the software described in this advisory.|
Avaya recommends that customers follow recommended actions supplied by the Operating System vendor (e.g. RedHat Linux) or remove the affected package.
Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.
ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.
V 1.0 - October 20, 2006 - Initial Statement issued.
V 2.0 - November 22, 2006 - Updated Actions for Avaya S87XX/S8500/S8300 to indicate there is now a load available that removes PHP from CM 2.x systems.
V 3.0 - October 10, 2008 - Updated Actions for Message Storage Server and SES. Changed the Advisory Status to Final.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or email@example.com.
© 2006 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.