ID CVE-2005-3164
Summary The AJP connector in Apache Tomcat 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standalone, does not properly handle when a connection is broken before request body data is sent in a POST request, which can lead to an information leak when "unsuitable request body data" is used for a different request, possibly related to Java Servlet pages.
References
Vulnerable Configurations
  • Apache Software Foundation Tomcat 4.0.1
    cpe:2.3:a:apache:tomcat:4.0.1
  • Apache Software Foundation Tomcat 4.0.2
    cpe:2.3:a:apache:tomcat:4.0.2
  • Apache Software Foundation Tomcat 4.0.3
    cpe:2.3:a:apache:tomcat:4.0.3
  • Apache Software Foundation Tomcat 4.0.4
    cpe:2.3:a:apache:tomcat:4.0.4
  • Apache Software Foundation Tomcat 4.0.5
    cpe:2.3:a:apache:tomcat:4.0.5
  • Apache Software Foundation Tomcat 4.0.6
    cpe:2.3:a:apache:tomcat:4.0.6
  • Apache Software Foundation Tomcat 4.1.0
    cpe:2.3:a:apache:tomcat:4.1.0
  • Apache Software Foundation Tomcat 4.1.1
    cpe:2.3:a:apache:tomcat:4.1.1
  • Apache Software Foundation Tomcat 4.1.2
    cpe:2.3:a:apache:tomcat:4.1.2
  • Apache Software Foundation Tomcat 4.1.3
    cpe:2.3:a:apache:tomcat:4.1.3
  • Apache Software Foundation Tomcat 4.1.3 beta
    cpe:2.3:a:apache:tomcat:4.1.3:beta
  • Apache Software Foundation Tomcat 4.1.10
    cpe:2.3:a:apache:tomcat:4.1.10
  • Apache Software Foundation Tomcat 4.1.12
    cpe:2.3:a:apache:tomcat:4.1.12
  • Apache Software Foundation Tomcat 4.1.15
    cpe:2.3:a:apache:tomcat:4.1.15
  • Apache Software Foundation Tomcat 4.1.24
    cpe:2.3:a:apache:tomcat:4.1.24
  • Apache Software Foundation Tomcat 4.1.28
    cpe:2.3:a:apache:tomcat:4.1.28
  • Apache Software Foundation Tomcat 4.1.31
    cpe:2.3:a:apache:tomcat:4.1.31
  • Apache Software Foundation Tomcat 4.1.36
    cpe:2.3:a:apache:tomcat:4.1.36
  • cpe:2.3:a:apache_software_foundation:tomcat:4.1
    cpe:2.3:a:apache_software_foundation:tomcat:4.1
  • cpe:2.3:a:apache_software_foundation:tomcat:4.1.32
    cpe:2.3:a:apache_software_foundation:tomcat:4.1.32
  • cpe:2.3:a:apache_software_foundation:tomcat:4.1.34
    cpe:2.3:a:apache_software_foundation:tomcat:4.1.34
  • cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_e
    cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_e
  • cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_f
    cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_f
  • cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_h
    cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_h
  • cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_k
    cpe:2.3:a:hitachi:cosminexus_application_server:05_00_05_05_k
CVSS
Base: 2.6 (as of 06-10-2005 - 08:44)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK HIGH NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2008-004.NASL
    description The remote host is running a version of Mac OS X 10.4 that does not have the security update 2008-004 applied. This update contains security fixes for a number of programs.
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 33282
    published 2008-07-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=33282
    title Mac OS X Multiple Vulnerabilities (Security Update 2008-004)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_10_5_4.NASL
    description The remote host is running a version of Mac OS X 10.5.x that is prior to 10.5.4. Mac OS X 10.5.4 contains security fixes for multiple components.
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 33281
    published 2008-07-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=33281
    title Mac OS X 10.5.x < 10.5.4 Multiple Vulnerabilities
  • NASL family Web Servers
    NASL id TOMCAT_4_1_37.NASL
    description According to its self-reported version number, the instance of Apache Tomcat 4.x listening on the remote host is prior to 4.1.37. It is, therefore, affected by the following vulnerabilities : - The remote Apache Tomcat install may be vulnerable to an information disclosure attack if the deprecated AJP connector processes a client request having a non-zero Content-Length and the client disconnects before sending the request body. (CVE-2005-3164) - The remote Apache Tomcat install may be vulnerable to a cross-site scripting attack if the JSP and Servlet examples are enabled. Several of these examples do not properly validate user input. (CVE-2007-1355, CVE-2007-2449) - The remote Apache Tomcat install may be vulnerable to a cross-site scripting attack if the Manager web application is enabled as it fails to escape input data. (CVE-2007-2450) - The remote Apache Tomcat install may be vulnerable to an information disclosure attack via cookies. Apache Tomcat treats the single quote character in a cookie as a delimiter which can lead to information, such as session ID, to be disclosed. (CVE-2007-3382) - The remote Apache Tomcat install may be vulnerable to a cross-site scripting attack if the SendMailServlet is enabled. The SendMailServlet is a part of the examples web application and, when reporting error messages, fails to escape user provided data. (CVE-2007-3383) - The remote Apache Tomcat install may be vulnerable to an information disclosure attack via cookies. The previous fix for CVE-2007-3385 was incomplete and did not account for the use of quotes or '%5C' in cookie values. (CVE-2007-3385, CVE-2007-5333) - The remote Apache Tomcat install may be vulnerable to an information disclosure attack via the WebDAV servlet. Certain WebDAV requests, containing an entity with a SYSTEM tag, can result in the disclosure of arbitrary file contents. (CVE-2007-5461) Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number..
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 47030
    published 2010-06-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=47030
    title Apache Tomcat 4.x < 4.1.37 Multiple Vulnerabilities
refmap via4
apple APPLE-SA-2008-06-30
bid 15003
confirm
jvn JVN#79314822
mlist
  • [tomcat-dev] 20190319 svn commit: r1855831 [21/30] - in /tomcat/site/trunk: ./ docs/ xdocs/
  • [tomcat-dev] 20190325 svn commit: r1856174 [19/29] - in /tomcat/site/trunk: docs/ xdocs/ xdocs/stylesheets/
secunia
  • 17019
  • 30802
  • 30899
  • 30908
sunalert 239312
vupen
  • ADV-2008-1979
  • ADV-2008-1981
Last major update 17-10-2011 - 00:00
Published 06-10-2005 - 06:02
Last modified 25-03-2019 - 07:29
Back to Top