PHP is a general purpose scripting language widely used in World Wide Web (WWW) pages and applications.
PHP's handling of deeply nested arrays was found to contain a possible Denial of Service (DoS) condition. This issue could possibly be triggered if an attacker submitted an input variable with a deeply nested array. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1285 to this issue.
The unserialize() PHP function was found to contain a security issue. If a PHP application passed arbitrary data to the unserialize() function, it is possible that the arbitrary data would be executed as the user running the HTTP daemon. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1286 to this issue.
PHP's mb_parse_str() function was found to contain an issue when setting global variables. If a PHP script used the mb_parse_str() function, it could possibly be used to force the enablement of the register_globals configuration parameter. If this happened, it could allow for global variables to be injected into a PHP environment. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1583 to this issue.
PHP's session_decode() function was found to contain a double free security issue. If a PHP application passed arbitrary data to the session_decode() function, it is possible that the arbitrary data would be executed as the user running the HTTPdaemon. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1711 to this issue.
PHP's mail() function was found to contain a bug when processing e-mail header data. If the mail() function processed an email with a carefully crafted Subject header, it is possible to send arbitrary e-mail to arbitrary recipients. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1718 to this issue.
PHP's gd extension was found to contain a buffer overflow vulnerability. If a malicious user could get a PHP script to process a specially crafted WBMP image file, it could possibly allow for arbitrary code execution. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1001 to this issue.
PHP's gd extension was found to contain a buffer over-read condition. The PHP interpreter could possibly crash if a script was made to write arbitrary strings in a JIS font. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-0455 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 Communication Manager | CM 2.x CM 4.0 |
Low | For CM 2.x installations, upgrade to CM 2.2 Load 127 or later. For CM 4.0, Avaya recommends upgrading to CM 5.0 to resolve these issues. |
| Avaya Messaging Storage Server | MSS 3.0 | Low | Upgrade to MSS 3.1 or later. |
| Avaya SIP Enablement Services | SES 3.1.x, 4.0 | Low | Avaya recommends upgrading to SES 5.0 to resolve these issues. |
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 vendor's 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 | Low | See recommended actions below. |
Recommended Actions:
Avaya recommends that customers follow
recommended actions supplied by 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 BUT NOT LIMITED TO 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, INCIDENTAL, STATUTORY, 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 - June 29, 2007 - Initial Statement issued.
V 2.0 - March 19, 2008 - Updated the Recommended Actions for CM and SES and
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 protected].
© 2008 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.