CVE-2008-5515

Public on

Last Modified: UTC

Important Important Impact What does this mean?

Description

The MITRE CVE dictionary describes this issue as

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalizes the target pathname before filtering the query string when using the RequestDispatcher method, which allows remote attackers to bypass intended access restrictions and conduct directory traversal attacks via .. (dot dot) sequences and the WEB-INF directory in a Request.

Additional Information

External References

Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2008-5515

Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2008-5515

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
JBEAP 4.2.0 for RHEL 4 hibernate3 Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 hibernate3-annotations Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 hibernate3-commons-annotations Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 hibernate3-entitymanager Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 hibernate3-validator Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 hsqldb Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 jakarta-slide-webdavclient Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 jboss-cache Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 jboss-remoting Fixed This content is not included.RHSA-2009:1144
JBEAP 4.2.0 for RHEL 4 jboss-seam Fixed This content is not included.RHSA-2009:1144
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.