CVE Vulnerabilities

CVE-2007-5333

Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 12, 2008 | Modified: Nov 07, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

Apache Tomcat 6.0.0 through 6.0.14, 5.5.0 through 5.5.25, and 4.1.0 through 4.1.36 does not properly handle (1) double quote () characters or (2) %5C (encoded backslash) sequences in a cookie value, which might cause sensitive information such as session IDs to be leaked to remote attackers and enable session hijacking attacks. NOTE: this issue exists because of an incomplete fix for CVE-2007-3385.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 4.1.0 (including) 4.1.36 (including)
Tomcat Apache 5.5.0 (including) 5.5.25 (including)
Tomcat Apache 6.0.0 (including) 6.0.14 (including)
JBEWS 1.0 for RHEL 4 RedHat tomcat5-0:5.5.23-1.patch07.19.ep5.el4 *
Red Hat Certificate System 7.3 RedHat ant-0:1.6.5-1jpp_1rh *
Red Hat Certificate System 7.3 RedHat avalon-logkit-0:1.2-2jpp_4rh *
Red Hat Certificate System 7.3 RedHat axis-0:1.2.1-1jpp_3rh *
Red Hat Certificate System 7.3 RedHat classpathx-jaf-0:1.0-2jpp_6rh *
Red Hat Certificate System 7.3 RedHat classpathx-mail-0:1.1.1-2jpp_8rh *
Red Hat Certificate System 7.3 RedHat geronimo-specs-0:1.0-0.M4.1jpp_10rh *
Red Hat Certificate System 7.3 RedHat jakarta-commons-modeler-0:2.0-3jpp_2rh *
Red Hat Certificate System 7.3 RedHat log4j-0:1.2.12-1jpp_1rh *
Red Hat Certificate System 7.3 RedHat mx4j-1:3.0.1-1jpp_4rh *
Red Hat Certificate System 7.3 RedHat pcsc-lite-0:1.3.3-3.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-ca-0:7.3.0-20.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-java-tools-0:7.3.0-10.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-kra-0:7.3.0-14.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-manage-0:7.3.0-19.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-native-tools-0:7.3.0-6.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-ocsp-0:7.3.0-13.el4 *
Red Hat Certificate System 7.3 RedHat rhpki-tks-0:7.3.0-13.el4 *
Red Hat Certificate System 7.3 RedHat tomcat5-0:5.5.23-0jpp_4rh.16 *
Red Hat Certificate System 7.3 RedHat xerces-j2-0:2.7.1-1jpp_1rh *
Red Hat Certificate System 7.3 RedHat xml-commons-0:1.3.02-2jpp_1rh *
Red Hat Developer Suite V.3 RedHat tomcat5-0:5.5.23-0jpp_18rh *
Red Hat Enterprise Linux 5 RedHat tomcat5-0:5.5.23-0jpp.7.el5_3.2 *
Red Hat JBoss Enterprise Web Server 1 for RHEL 5 RedHat tomcat5-0:5.5.23-0jpp.9.6.ep5.el5 *
Red Hat Network Satellite Server v 5.2 RedHat tomcat5-0:5.5.23-0jpp_18rh *
Red Hat Network Satellite Server v 5.3 RedHat tomcat5-0:5.5.23-0jpp_18rh *
RHAPS Version 2 for RHEL 4 RedHat tomcat5-0:5.5.23-0jpp_4rh.16 *
Tomcat5 Ubuntu dapper *
Tomcat5 Ubuntu edgy *
Tomcat5 Ubuntu feisty *
Tomcat5.5 Ubuntu edgy *
Tomcat5.5 Ubuntu feisty *
Tomcat5.5 Ubuntu gutsy *
Tomcat5.5 Ubuntu hardy *
Tomcat5.5 Ubuntu upstream *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References