The RPM Package Manager (RPM) is a command line driven package management system capable of installing, uninstalling, verifying, querying, and updating software packages.
Multiple flaws were found in the way the RPM library parsed package headers. An attacker could create a specially-crafted RPM package that, when queried or installed, would cause rpm to crash or, potentially, execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3378 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by Red Hat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Application Enablement Services||4.x, 5.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Aura® Application Server 5300:
||2.x including PB1 through PB18||Low||Upgrade to 2.0 PB19 or later.|
|Avaya Aura® Communication Manager||6.0.x, 5.2, 5.2.1 including SSP1 and SSP2||Low||For 5.2 and earlier, upgrade to 5.2.1 and install
Security Service Pack 3 or later.
For 5.2.1, install Security Service Pack 3 or later.
For 6.0.x, upgrade to 6.2 or later.
|Avaya Communication Server 1000:
||6.x, 7.x||Low||See recommended actions and mitigating factors table below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® Conferencing Standard Edition||6.x||Low||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 7.0 or later.|
|Avaya IP Office Application Server||6.x, 7.x, 8.x||Low||Upgrade to 9.0 or later.|
|Avaya IQ||5.2 thru 5.2.5||Low||Upgrade to IQ 5.2.6 and install Patch 2 or later.|
|Avaya Meeting Exchange||5.x||Low||Upgrade to 6.2 or later.|
|Avaya Message Networking||5.2 through 5.2.4||Low||Upgrade to 5.2.5 or later.|
|Avaya Aura® Messaging||6.0.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Message Storage Server||5.2 through 5.2.13||Low||Upgrade to 5.2.14 or later.|
|Avaya Aura® Presence Services||6.0. 6.1, 6.1.1||Low||Upgrade to 6.1.2 or later.|
|Avaya Proactive Contact||4.x, 5.0.x||Low||Upgrade to 5.1 or later.|
|Avaya Aura® Session Manager||5.x, 6.0.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Aura® SIP Enablement Services||4.0.x thru 5.2, 5.2.1 including SSP1 and SSP2||Low||For 5.2 and earlier, upgrade to 5.2.1 and install
Security Service Pack 3 or later.
For 5.2.1, install Security Service Pack 3 or later.
|Avaya Aura® System Manager||5.x, 6.0.x, 6.1.x, 6.2.x, 6.3.1||Low||Upgrade to 6.3 or later.|
|Avaya Aura® System Platform||1.1, 6.0 through 6.0.3 including patches up to 126.96.36.199.3||Low||Upgrade to 188.8.131.52.3 and install patch 184.108.40.206.3 or later.|
|Avaya Aura® Communication Manager Utility Services||6.0.x, 6.1.x, 6.2 through 220.127.116.11.15||Low||For 6.0 and 6.1, upgrade to 6.2 and install Service Pack
18.104.22.168.15 or later.
For 6.2, install Service Pack 22.214.171.124.15 or later
|Avaya Voice Portal||5.0.x, 5.1 including SP1||Low||Upgrade to Avaya Linux for Voice Portal 5.1 SP2 and Voice Portal SP2 or later.|
Recommended Actions for System Products:
Avaya strongly recommends that customers follow networking and security best practices by implementing firewalls, ACLs, physical security or other appropriate access restrictions. Though Avaya believes such restrictions should always be in place, risk to Avaya products and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as an Avaya provided product update or the recommended Avaya action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period, but customers should not modify the System Product operating system or application unless the change is approved by Avaya. Making changes that are not approved may void the Avaya product service contract.
When determining risk, Avaya takes into account many factors as outlined by Avaya's Security Vulnerability Classification Policy. The following table describes factors that mitigate the risk of specific vulnerabilities for affected Avaya products:
||This is a low risk as usage of the rpm command to install package not provided by Avaya would constitute non-standard user interaction.|
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.
|Avaya Aura® Application Enablement Services 4.x/5.x||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|Avaya Aura® Experience Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the EP application.|
|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.|
|Avaya Aura® Presence Services||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Aura® System Manager 1.0||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application.|
|Avaya Voice Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the VP application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by Red Hat regarding their Enterprise 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 29, 2011 - Initial Statement issued.
V 2.0 - April 6, 2012 - Changed AS5300, CM, PS, SM and VP affected versions and actions.
V 3.0 - August 29, 2012 - Changed AES and SP affected versions and actions.
V 4.0 - December 21, 2012 - Changed MN, Messaging, MSS, Utility Services and CS1000 affected versions and actions.
V 5.0 - March 26, 2013 - Changed PC and MX affected versions and actions.
V 6.0 - April 19, 2013 - Changed CM and SES affected versions and actions.
V 7.0 - May 24, 2013 - Changed SMGR affected versions and actions.
V 8.0 - June 26, 2013 - Changed Conferencing SE actions.
V 9.0 - October 29, 2013 - Changed IPOAS affected versions and actions.
V 10.0 - June 25, 2015 - Changed IQ affected versions and actions, and set 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 firstname.lastname@example.org.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2011 Avaya Inc. All Rights Reserved. All trademarks identifying Avaya products by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.