libxslt is a library for transforming XML files into other textual formats (including HTML, plain text, and other XML representations of the underlying data) using the standard XSLT stylesheet transformation mechanism.
A heap-based buffer overflow flaw was found in the way libxslt applied templates to nodes selected by certain namespaces. An attacker could use this flaw to create a malicious XSL file that, when used by an application linked against libxslt to perform an XSL transformation, could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-2871 to this issue.
Several denial of service flaws were found in libxslt. An attacker could use these flaws to create a malicious XSL file that, when used by an application linked against libxslt to perform an XSL transformation, could cause the application to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-2825, CVE-2012-2870 and CVE-2011-3970 to these issues.
An information leak could occur if an application using libxslt processed an untrusted XPath expression, or used a malicious XSL file to perform an XSL transformation. If combined with other flaws, this leak could possibly help an attacker bypass intended memory corruption protections. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1202 to this issue.
A double free vulnerability in libxslt, as used in Google Chrome before 22.0.1229.79, could allow remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to XSL transforms. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-2893 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 | 6.2.x and earlier | Low | Upgrade to 6.3 or later. |
| Avaya IQ | 5.0 thru 5.2.5 | Low | Upgrade to 5.2.6 and install Patch 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® Experience Portal | 6.x | Low | Upgrade to 7.0 or later. |
| Avaya IP Office Server Edition | 8.x | Low | Upgrade to 9.0 or later. |
| Avaya Aura® Messaging | 6.0 thru 6.2.x | Low | Ugrade to 6.3 or later. |
| Avaya one-X® Client Enablement Services | 6.1 including SP1 and SP2 | Low | Upgrade to 6.1 SP3 or later. |
| Avaya Aura® Presence Services | 6.x | Low | Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com. |
| Avaya Aura® Session Manager | 6.3.1 and earlier | Low | Upgrade to 6.3.2 or later. |
| Avaya Aura® System Manager | 6.3.1 and ealier | Low | Upgrade to 6.3.2 or later. |
| Avaya Aura® System Platform | 6.2.2 and earlier | Low | Upgrade to 6.3 or later. |
| Avaya Aura® Communication Manager Utility Services | 6.0.x, 6.1.x, 6.2 | Low | For 6.0 and 6.1, upgrade to 6.2 and install Service Pack 6.2.5.0.15 or later. For 6.2, install Service Pack 6.2.5.0.15 or later. |
| Avaya Voice Portal | 5.x | Low | Upgrade to Experience Portal 7.0 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:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2011-1202 CVE-2011-3970 CVE-2012-2825 CVE-2012-2870 CVE-2012-2871 |
These are a low risk for CS1000 as the package is installed but not used. These are a low risk for all other listed products as exploitation would require privileged account access and not provide any additional capabilities. |
|
CVE-2012-2893 |
There is no risk as the package version installed is not affected. |
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: | Actions: |
|---|---|
| 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 Secure Access Link Gateway | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SAL Gateway 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 14, 2012 - Initial Statement issued.
V 2.0 - March 8, 2013 - Updated CMUS affected versions and actions.
V 3.0 - April 2, 2013 - Added CVE-2012-2893 to overview and mitigating factors and updated CES affected versions and actions.
V 4.0 - May 28, 2013 - Updated AES, CS1000, SM, SMGR and SP affected versions and actions.
V 5.0 - October 8, 2013 - Updated IPO actions.
V 6.0 - January 8, 2014 - Updated EP and VP actions.
V 7.0 - March 21, 2014 - Updated Messaging affected versions and actions.
V 8.0 - September 8, 2015 - Updated IQ and PS 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 [email protected].
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2012 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.