The HTML Manager interface displayed web applciation provided data, such as display names, without filtering. A malicious web application could trigger script execution by an administartive user when viewing the manager pages.
Versions Affected:
- - Tomcat 7.0.0 to 7.0.5
- - Tomcat 6.0.0 to 6.0.29
- - Tomcat 5.5.0 to 5.5.31
More information about this vulnerability can be found in the security advisory issued by Apache Tomcat:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 5.2 thru 5.2.2, 6.1 | Low | For Application Enablement Services 5.2 thru 5.2.2, upgrade to 5.2.3 or later. For Application Enablement Services 6.1, upgrade to 6.1.1 or later. |
| Avaya Aura® Communication Manager | 5.x | Low | Upgrade to Communication Manager 6.0 or use the workaround in the Mitigating Factors Table below. |
| Avaya Aura® Conferencing Standard Edition | 6.0 including 6.0 SP1 | 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 Meeting Exchange | 5.x | Low | Upgrade to Avaya Meeting Exchange 6.2 or later. |
| Avaya Aura® Presence Services | 5.2.x through 6.1 | Low | Upgrade to Avaya Aura® Presence Services 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1, 5.2, 6.0, 6.1 | None | See Mitigating Factors Table below. |
| Avaya Aura® System Manager | 5.2.x thru 6.2.x | Low | Upgrade to Avaya Aura® System Manager 6.3 or later |
| Avaya Voice Portal | 5.x | Low | Upgrade to Avaya Aura® Experience Portal 6.0. |
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-0013 |
For CM 5.x, a workaround is to use the Web Access Mask page to only
allow certain profiles access to the Avaya Installation Wizard (AIW) and Network Region Wizard (NRW) functionality. Rated a None Risk for Session Manager since Tomcat is not accessible on the SM SIPAS container as http ports are not enabled. Rated a Low Risk for all other products since Administrative privileges are required to exploit this vulnerability. |
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 - April 25, 2011 - Initial Statement issued.
V 2.0 - May 8, 2012 - Updated CM actions.
V 3.0 - May 16, 2012 - Updated AES actions.
V 4.0 - June 1, 2012 - Updated VP actions.
V 5.0 - September 11, 2012 - Removed Session Manager as it is a None risk.
V 6.0 - September 12, 2012 - Added Session Manager as a None risk with Mitigating Factors explaination.
V 7.0 - October 11, 2013 - Updated SMGR, Conferencing SE, MX and PS affected versions and actions and ASA 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].
© 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.