PHP is a general purpose scripting language widely used in World Wide Web (WWW)pages and applications.
PHP's phpinfo() function was found to contain an issue in how it sanitized long strings. If an attacker could identify a site using the phpinfo() call in publicly-available PHP programs, they could possibly use cross-site scriptings attacks against the site. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-0996 to this issue.
PHP's html_entity_decode() function was discovered not to properly handle binary content. This could possibly allow a malicious user to disclose the contents of a certain part of memory. To take advantage of this, an attacker would have to find a site using the html_entity_decode() function accepting untrusted input from users and showing the results. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-1490 to this issue.
A bug was found in PHP's error handling output that, under certain conditions, would not properly escape HTML output. If a site had both the "display_errors" and "html_errors" PHP enabled, an attacker could possibly take advantage of this vulnerability to use cross-site scripting attacks against the site. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-0208 to the issue.
The mb_send_mail() function in PHP was found to contain an input validation issue. Utilizing this bug, an attacker could inject arbitrary e-mail headers into an email sent by a script calling the mb_send_mail() function, particularly where the "To" e-mail header can be set by the attacker. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-3883 to this issue.
The IMAP server provided by the University of Washington (uw-imap) was found to contain a buffer overflow vulnerability. As the php-imap package in Red Hat Enterprise Linux 3 was compiled against the static c-client libraries from the vulnerable version of uw-imap, php-imap needed to be rebuilt against the fixed version of uw-imap. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-2933 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 Intuity LX||IALX 1.x||Low||Update to IALX 2.0 or later.|
|Avaya Messaging Storage Server||MSS 1.x - 2.x||Low||Upgrade to MSS 3.0 or later.|
|Avaya Message Networking||MN 1.x - 3.0||Low||Update to MN 3.1 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:|
|Avaya Interactive Response(IR)||All||None||Depending on the Operating System provided by customers, the affected packages may be installed on the underlying Operating System supporting the IR application. The IR application does not require the software described in this advisory.|
|CVLAN||All||None||Depending on the Operating System provided by customers, the affected packages 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||Low||See recommended actions below.|
Avaya recommends installing the appropriate patch from the Operating System Vendor (e.g. Red Hat).
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 - July 5, 2006 - Initial Statement issued.
V 2.0 - August 25, 2006 - Changed ASA Status from Final to Interim and changed the Affected Versions for Avaya S87XX/S8500/S8300 from 2.x to 1.x - 2.x based on further review.
V 3.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 4.0 - February 22, 2008 - Updated Actions for the IALX, MSS and MN System Products as well as set 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.