CVE-2015-5174: Path Traversal

Published Sep 23, 2015
·
Updated

Directory traversal vulnerability in RequestUtil.java in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.65, and 8.x before 8.0.27 allows remote authenticated users to bypass intended SecurityManager restrictions and list a parent directory via a /.. (slash dot dot) in a pathname used by a web application in a getResource, getResourceAsStream, or getResourcePaths call, as demonstrated by the $CATALINABASE/webapps directory.

Other sources

URL Normalisation issue

A directory traversal vulnerability exists in RequestUtil.java in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.65, and 8.x before 8.0.27 that allows a remote authenticated users to bypass intended SecurityManager restrictions and list a parent directory via a /.. (slash dot dot) in a pathname used by a web application in a getResource, getResourceAsStream, or getResourcePaths call, as demonstrated by the $CATALINABASE/webapps directory.

Red Hat

Affected Software

99 affected componentsFixes available
redhat/tomcat<6.0.45
6.0.45
redhat/tomcat<7.0.65
7.0.65
redhat/tomcat<8.0.27
8.0.27
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Apache Tomcat=6.0.0
Apache Tomcat=6.0.0-alpha
Apache Tomcat=6.0.1
Apache Tomcat=6.0.1-alpha
Apache Tomcat=6.0.2
Apache Tomcat=6.0.2-alpha
Apache Tomcat=6.0.2-beta
Apache Tomcat=6.0.4
Apache Tomcat=6.0.4-alpha
Apache Tomcat=6.0.10
Apache Tomcat=6.0.11
Apache Tomcat=6.0.13
Apache Tomcat=6.0.14
Apache Tomcat=6.0.16
Apache Tomcat=6.0.18
Apache Tomcat=6.0.20
Apache Tomcat=6.0.24
Apache Tomcat=6.0.26
Apache Tomcat=6.0.28
Apache Tomcat=6.0.29
Apache Tomcat=6.0.30
Apache Tomcat=6.0.32
Apache Tomcat=6.0.33
Apache Tomcat=6.0.35
Apache Tomcat=6.0.36
Apache Tomcat=6.0.37
Apache Tomcat=6.0.39
Apache Tomcat=6.0.41
Apache Tomcat=6.0.43
Apache Tomcat=6.0.44
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.2-beta
Apache Tomcat=7.0.4-beta
Apache Tomcat=7.0.5-beta
Apache Tomcat=7.0.6
Apache Tomcat=7.0.10
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.14
Apache Tomcat=7.0.16
Apache Tomcat=7.0.19
Apache Tomcat=7.0.20
Apache Tomcat=7.0.21
Apache Tomcat=7.0.22
Apache Tomcat=7.0.23
Apache Tomcat=7.0.25
Apache Tomcat=7.0.26
Apache Tomcat=7.0.27
Apache Tomcat=7.0.28
Apache Tomcat=7.0.29
Apache Tomcat=7.0.30
Apache Tomcat=7.0.32
Apache Tomcat=7.0.33
Apache Tomcat=7.0.34
Apache Tomcat=7.0.35
Apache Tomcat=7.0.37
Apache Tomcat=7.0.39
Apache Tomcat=7.0.40
Apache Tomcat=7.0.41
Apache Tomcat=7.0.42
Apache Tomcat=7.0.47
Apache Tomcat=7.0.50
Apache Tomcat=7.0.52
Apache Tomcat=7.0.53
Apache Tomcat=7.0.54
Apache Tomcat=7.0.55
Apache Tomcat=7.0.56
Apache Tomcat=7.0.57
Apache Tomcat=7.0.59
Apache Tomcat=7.0.61
Apache Tomcat=7.0.62
Apache Tomcat=7.0.63
Apache Tomcat=7.0.64
Apache Tomcat=8.0.0-rc1
Apache Tomcat=8.0.0-rc10
Apache Tomcat=8.0.0-rc3
Apache Tomcat=8.0.0-rc5
Apache Tomcat=8.0.1
Apache Tomcat=8.0.11
Apache Tomcat=8.0.12
Apache Tomcat=8.0.14
Apache Tomcat=8.0.15
Apache Tomcat=8.0.17
Apache Tomcat=8.0.18
Apache Tomcat=8.0.20
Apache Tomcat=8.0.21
Apache Tomcat=8.0.22
Apache Tomcat=8.0.23
Apache Tomcat=8.0.24
Apache Tomcat=8.0.26
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=15.10
Canonical Ubuntu Linux=16.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.45
  2. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.65
  3. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.27
  4. Upgrade

    Upgrade Apache Tomcat 6.x to a version that resolves this vulnerability.

    Fixed in 6.0.45
  5. Upgrade

    Upgrade Apache Tomcat 7.x to a version that resolves this vulnerability.

    Fixed in 7.0.65
  6. Upgrade

    Upgrade Apache Tomcat 8.x to a version that resolves this vulnerability.

    Fixed in 8.0.27

Event History

Sep 23, 2015
Data Sourced
via Red Hat·01:47 PM
DescriptionSeverityAffected Software
Feb 25, 2016
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2015-5174?

CVE-2015-5174 has been classified as a medium severity vulnerability.

2

How do I fix CVE-2015-5174?

To fix CVE-2015-5174, upgrade Apache Tomcat to versions 6.0.45, 7.0.65, or 8.0.27 and above.

3

Who is affected by CVE-2015-5174?

CVE-2015-5174 affects Apache Tomcat versions prior to 6.0.45, 7.0.65, and 8.0.27.

4

What type of vulnerability is CVE-2015-5174?

CVE-2015-5174 is a directory traversal vulnerability that allows authenticated users to bypass security restrictions.

5

What are the consequences of CVE-2015-5174?

Exploiting CVE-2015-5174 could allow an attacker to list parent directories and access restricted files on the server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203