Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies. The Apache Tomcat MemoryUserDatabase can create log entries containing passwords upon encountering errors in JMX user creation,
which allows local users to obtain sensitive information by reading a log file. The Common Vulnerabilities and Exposures project (cve.mitre.org)
has assigned the name
CVE-2011-2204 to this issue.
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.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Aura® Application Server 5300:
||1.0.x, 2.0.x, 3.0||Low||
Application Server 5300 2.0 PB15 and earlier, upgrade to 2.0 PB16 or later.
|Avaya Aura® Communication Manager||5.x||Low||Upgrade to Communication Manager 6.0 or later.|
|Avaya Communication Server 1000:
||7.0, 7.5||Low||See Mitigating Factors Table below.|
|Avaya Aura® Conferencing Standard Edition||6.0 including 6.0SP1||Low||See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy|
|Avaya IP Office Application Server||6.1, 7.0||Low||See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy|
|Avaya IQ||5.x||Low||See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy|
|Avaya Aura® Presence Services||5.2.x through 6.1.x||Low|
|Avaya Aura® SIP Enablement Services||4.0.x through 5.2.x||Low||See recommended actions below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® System Manager||5.2.x through 6.1.x||Low|
|Avaya Aura® System Platform||1.1, 6.0, 6.2||Low||Upgrade to Service Pack 188.8.131.52.9 or later.|
|Avaya Aura® Communication Manager Utility Services||6.0, 6.1||Low||Upgrade to 6.2 or later.|
|Avaya Voice Portal||5.0.x, 5.1, 5.1.1, 5.1.2||Low||Upgrade to Voice Portal 5.1.3 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:
||Avaya Communication Server 1000 does not use the vulnerable functionality, thus no upgrades are planned.
Rated a Low for other products since this exploit requires elevated privileges by a local user.
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 - September 5, 2011 - Initial Statement issued.
V 2.0 - September 6, 2012 - Updated CM, CS1000 Actions; removed SM product (not vulnerable).
V 3.0 - December 3, 2012 - Updated AS5300 and VP Actions.
V 4.0 - December 4, 2012 - Corrected VP Actions.
V 5.0 - April 2, 2013 - Updated AES, SP and US affected versions and actions.
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.
© 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.