The default SSL cipher configuration in Apache Tomcat 4.1.28 through 4.1.31, 5.0.0 through 5.0.30, and 5.5.0 through 5.5.17 uses certain insecure ciphers, including the anonymous cipher, which allows remote attackers to obtain sensitive information or have other, unspecified impacts.

According to its self-reported version number, the instance of Apache Tomcat 4.x listening on the remote host is prior to 4.1.32. It is, therefore, affected by the following vulnerabilities :

  - The remote Apache Tomcat install is vulnerable to a     denial of service attack. If directory listing is     enabled, function calls to retrieve the contents of     large directories can degrade performance.
    (CVE-2005-3510)

  - The remote Apache Tomcat install may be vulnerable to     a cross-site scripting attack if the JSP examples are     enabled. Several of these JSP examples do not properly     validate user input. (CVE-2005-4838)

  - The remote Apache Tomcat install allows remote users     to list the contents of a directory by placing a     semicolon before a filename with a mapped extension.
    (CVE-2006-3835)

  - If enabled, the JSP calendar example application is     vulnerable to a cross-site scripting attack because     user input is not properly validated. (CVE-2006-7196)

  - The remote Apache Tomcat install, in its default     configuration, permits the use of insecure ciphers when     using SSL. (CVE-2007-1858)

  - The remote Apache Tomcat install may be vulnerable to an     information disclosure attack by allowing requests from     a non-permitted IP address to gain access to a context     that is protected with a valve that extends     RequestFilterValve. (CVE-2008-3271)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Updated tomcat packages that fix multiple security issues are now available for Red Hat Network Satellite Server.

This update has been rated as having moderate security impact by the Red Hat Security Response Team.

Tomcat is a servlet container for Java Servlet and JavaServer Pages technologies.

It was reported Tomcat did not properly handle the following character sequence in a cookie: \' (a backslash followed by a double-quote). It was possible remote attackers could use this failure to obtain sensitive information, such as session IDs, for session hijacking attacks (CVE-2007-3385).

Tomcat was found treating single quote characters -- ' -- as delimiters in cookies. This could allow remote attackers to obtain sensitive information, such as session IDs, for session hijacking attacks (CVE-2007-3382).

The default Tomcat configuration permitted the use of insecure SSL cipher suites including the anonymous cipher suite. (CVE-2007-1858)

Tomcat permitted various characters as path delimiters. If Tomcat was used behind certain proxies and configured to only proxy some contexts, an attacker could construct an HTTP request to work around the context restriction and potentially access non-proxied content.
(CVE-2007-0450)

Directory listings were enabled by default in Tomcat. Information stored unprotected under the document root was visible to anyone if the administrator did not disable directory listings. (CVE-2006-3835)

It was found that generating listings of large directories was CPU intensive. An attacker could make repeated requests to obtain a directory listing of any large directory, leading to a denial of service. (CVE-2005-3510)

Tomcat was found to accept multiple content-length headers in a request. This could allow attackers to poison a web-cache, bypass web application firewall protection, or conduct cross-site scripting attacks. (CVE-2005-2090)

Users should upgrade to these erratum packages which contain an update to Tomcat that resolves these issues, and add the tyrex and jakarta-commons-pool packages which are required dependencies of the new Tomcat version.

This update of Tomcat fixes cross-site scripting bugs (CVE-2007-2449) as well as it improves the list of supported SSL ciphers.
(CVE-2007-1858)

The remote host supports the use of anonymous SSL ciphers. While this enables an administrator to set up a service that encrypts traffic without having to generate and configure SSL certificates, it offers no way to verify the remote host's identity and renders the service vulnerable to a man-in-the-middle attack.

Note: This is considerably easier to exploit if the attacker is on the same physical network.

This update of tomcat fixes cross-site-scripting bugs (CVE-2007-2449) as well as it improves the list of supported SSL ciphers (CVE-2007-1858).

This update of tomcat fixes cross-site scripting bugs (CVE-2007-2449) as well as it improves the list of supported SSL ciphers.
(CVE-2007-1858)

This update of tomcat improves the list of supported SSL ciphers (CVE-2007-1858).

ID	Name	Product	Family	Severity
47029	Apache Tomcat 4.x < 4.1.32 Multiple Vulnerabilities	Nessus	Web Servers	medium
43834	RHEL 3 / 4 : tomcat in Satellite Server (RHSA-2007:1069)	Nessus	Red Hat Local Security Checks	medium
41202	SuSE9 Security Update : Tomcat (YOU Patch Number 12116)	Nessus	SuSE Local Security Checks	medium
31705	SSL Anonymous Cipher Suites Supported	Nessus	Service detection	medium
31698	openSUSE 10 Security Update : tomcat55 (tomcat55-5069)	Nessus	SuSE Local Security Checks	medium
31675	openSUSE 10 Security Update : tomcat5 (tomcat5-5071)	Nessus	SuSE Local Security Checks	medium
31674	SuSE 10 Security Update : Tomcat 5 (ZYPP Patch Number 5070)	Nessus	SuSE Local Security Checks	medium
31673	openSUSE 10 Security Update : apache2-mod_jk (apache2-mod_jk-5066)	Nessus	SuSE Local Security Checks	low

Detections

Analytics

CVE-2007-1858

high

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

low