PHP is a general purpose scripting language widely used in World Wide Web (WWW) pages and applications.
PHP was found to contain a flaw in its tempnam() function. A remote attacker could potentially take advantage of the resulting directory traversal vulnerability and create files in arbitrary locations, bypassing the open_basedir parameter restrictions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-1494 to this issue.
A bug was found in PHP's wordwrap() function in how it checked for integer overflows. If an attacker could influence what was sent to the "break" parameter, a possible heap overflow condition could result. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-1990 to this issue.
Due to a bug found in PHP's zend_hash_del() function, a remote attacker could possibly force PHP to bypass the variable initialization stage in PHP scripts using the unset() PHP function. If the "register_globals" setting was enabled for PHP by default, this would result in a security issue. However as Red Hat Enterprise Linux has this disabled by default, it is not susceptible out of the box. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-3017 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 | All | Low | Upgrade to IA LX 2.0 to resolve this issue. |
| Avaya Messaging Storage Server | All | Low | Upgrade to IA MSS 3.1 to resolve this issue. |
| Avaya Message Networking | All | Low | Upgrade to IA MSS 3.1 to resolve this issue. |
| Avaya CCS/SES | 3.1.1 | Low | Upgrade to SES 3.1.2 or later to address this issue. |
Recommended Actions:
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 | None | Depending on the Operating System provided by customers, the affected packages may be installed on the underlying Operating System supporting the IMS application. The IMS application does not require the software described in this advisory. |
Recommended Actions:
Avaya recommends that customers follow
recommended actions supplied by the Operating System vendor (e.g.
RedHat
Linux) or remove the affected packages.
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 - August 31, 2006 - Initial Statement issued.
V 2.0 - September 1, 2006 - Added Avaya S87XX/S8500/S8300 Media
Gateways to
the affected system products after further review. Additionally
adjusted
the Risk Level of the ASA and of CCS/SES to Low.
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 - January 8, 2008 - Updated Actions for several products and
changed 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 protected].
© 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.