Apache Tomcat is a servlet container which powers various Java-based web tools.
A number of vulnerabilities have been reported in tomcat.
A vulnerability in the way tomcat accepts content-length headers could allow an attacker to poison a web-cache, bypass a web firewall, or conduct cross-site scripting (XSS) attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-2090 to this issue.
In some proxy configurations, a crafted HTTP request could be sent to view non-proxied content. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-0450 to this issue.
Several JSP examples display unfiltered values, which could allow a remote hacker to perform XSS attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2006-7195 and CVE-2006-7196 to these issues.
The default Tomcat configuration permits using insecure SSL cipher suites, including the anonymous cipher suite. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1858 to this issue.
Directory listings are enabled by default in Tomcat. In instances where the web server administrator has not disabled directory listings, all unprotected information in the document root is viewable. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-3835 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya AES | All | Low | Upgrade to AES 4.2.2. |
Recommended Actions:
For all system products which use vulnerable versions of
tomcat, 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.
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| CVLAN | All | None | 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) | All | None | 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. |
Recommended Actions:
Avaya recommends that customers follow recommended actions supplied by RedHat Linux or remove the affected package.
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 - May 31, 2007 - Initial Statement issued.
V 2.0 - June 22, 2009 - Updated actions for AES.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
© 2007 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.