PCRE is a Perl-compatible regular expression library.
A number of vulnerabilities have been discovered in the way pcre handles malformed regular expressions. An attacker could potentially exploit this vulnerability to run arbitrary code as the user running an application linked against pcre, such as grep. This vulnerability could lead to privilege escalation in certain circumstances. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-7224 to this issue.
This advisory is specific to an advisory released regarding Red Hat Enterprise Linux(RHEL) 4. Additional advisories may be published for versions of pcre shipped on different versions of RHEL.
A number of Avaya products have the pcre package installed. In certain systems, the pcre vulnerability could potentially be exploited to escalate privilege. In these cases the risk level is listed below as Medium, in accordance with Avaya's Vulnerability Classification Policy.
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 3.1.4, 4.0.1 and earlier, 5.0||Medium||CM 3.1.x - A patch is only available for CM 3.1.4 and may be
Please refer to Product Correction Notice (PCN)
CM 4.0.1/5.0 - A fix is available via Security Service Pack PLAT-rhel4-1000 or later. Security Service Packs may also be downloaded from here under the Software Downloads section. Please refer to PCN 1625P for details.
CM 5.1 and later than CM 4.0.1 - A fix is included in the release, there is no need to apply PLAT-rhel4-1000.
|Avaya Intuity AUDIX LX||IALX 2.0||Low||Upgrade to IALX 2.0 SP2 or later.|
|Avaya Messaging Storage Server||MSS 3.x, 4.0||Low||Upgrade to MSS 5.0 or later.|
|Avaya Message Networking||MN 3.1||Low||See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy|
|Avaya SIP Enablement Services||SES 3.1.x, 4.0 and 5.0||Medium||SES 3.1.x/4.0 - A fix is only available in the latest Service Pack
for SES 4.0 and may be downloaded from
Please refer to Product Correction Notice (PCN)
SES 5.0 - A fix is available via Security Service Pack PLAT-rhel4-1000 or later. Security Service Packs may also be downloaded from here under the Software Downloads section. Please refer to PCN 1626P for details.
SES 5.1 or later - A fix is included in the release, there is no need to apply PLAT-rhel4-1000.
|Avaya AES||AES 4.0.1, 4.1||Low||Upgrade to AES 4.2 or later.|
For all system products which use vulnerable versions of pcre, 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.
|CVLAN||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)||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.|
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by RedHat Linux.
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 - November 28, 2007 - Initial Statement issued.
V 2.0 - March 3, 2008 - Updated Communication Manager and SIP Enablement Services with available fixes.
V 3.0 - July 21, 2008 - Updated content with the release of Communication Manager 4.0.3/5.1, SIP Enablement Services 5.1 and AES 4.2.
V 4.0 - February 27, 2009 - Changed MSS affected versions and recommended actions, and IALX recommended actions.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or email@example.com.
© 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.