CVE-2017-12616: Infoleak

Published Sep 19, 2017
·
Updated

Last updated 25 August 2025

Other sources

When using a VirtualDirContext with Apache Tomcat 7.0.0 to 7.0.80 it was possible to bypass security constraints and/or view the source code of JSPs for resources served by the VirtualDirContext using a specially crafted request.

Affected Software

92 affected componentsFixes available
redhat/tomcat7<0:7.0.70-25.ep7.el6
0:7.0.70-25.ep7.el6
redhat/tomcat8<0:8.0.36-29.ep7.el6
0:8.0.36-29.ep7.el6
redhat/tomcat-native<0:1.2.8-11.redhat_11.ep7.el6
0:1.2.8-11.redhat_11.ep7.el6
redhat/tomcat-vault<0:1.1.6-1.Final_redhat_1.1.ep7.el6
0:1.1.6-1.Final_redhat_1.1.ep7.el6
redhat/tomcat7<0:7.0.70-25.ep7.el7
0:7.0.70-25.ep7.el7
redhat/tomcat8<0:8.0.36-29.ep7.el7
0:8.0.36-29.ep7.el7
redhat/tomcat-native<0:1.2.8-11.redhat_11.ep7.el7
0:1.2.8-11.redhat_11.ep7.el7
redhat/tomcat-vault<0:1.1.6-1.Final_redhat_1.1.ep7.el7
0:1.1.6-1.Final_redhat_1.1.ep7.el7
debian/tomcat7
redhat/tomcat<7.0.81
7.0.81
Apache Tomcat=7.0.0
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.2-beta
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.4-beta
Apache Tomcat=7.0.5
Apache Tomcat=7.0.5-beta
Apache Tomcat=7.0.6
Apache Tomcat=7.0.7
Apache Tomcat=7.0.8
Apache Tomcat=7.0.9
Apache Tomcat=7.0.10
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.13
Apache Tomcat=7.0.14
Apache Tomcat=7.0.15
Apache Tomcat=7.0.16
Apache Tomcat=7.0.17
Apache Tomcat=7.0.18
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.24
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.31
Apache Tomcat=7.0.32
Apache Tomcat=7.0.33
Apache Tomcat=7.0.34
Apache Tomcat=7.0.35
Apache Tomcat=7.0.36
Apache Tomcat=7.0.37
Apache Tomcat=7.0.38
Apache Tomcat=7.0.39
Apache Tomcat=7.0.40
Apache Tomcat=7.0.41
Apache Tomcat=7.0.42
Apache Tomcat=7.0.43
Apache Tomcat=7.0.44
Apache Tomcat=7.0.45
Apache Tomcat=7.0.46
Apache Tomcat=7.0.47
Apache Tomcat=7.0.48
Apache Tomcat=7.0.49
Apache Tomcat=7.0.50
Apache Tomcat=7.0.51
Apache Tomcat=7.0.54
Apache Tomcat=7.0.55
Apache Tomcat=7.0.56
Apache Tomcat=7.0.57
Apache Tomcat=7.0.58
Apache Tomcat=7.0.59
Apache Tomcat=7.0.60
Apache Tomcat=7.0.61
Apache Tomcat=7.0.62
Apache Tomcat=7.0.63
Apache Tomcat=7.0.64
Apache Tomcat=7.0.65
Apache Tomcat=7.0.66
Apache Tomcat=7.0.67
Apache Tomcat=7.0.68
Apache Tomcat=7.0.69
Apache Tomcat=7.0.70
Apache Tomcat=7.0.71
Apache Tomcat=7.0.72
Apache Tomcat=7.0.73
Apache Tomcat=7.0.74
Apache Tomcat=7.0.75
Apache Tomcat=7.0.76
Apache Tomcat=7.0.77
Apache Tomcat=7.0.79
Apache Tomcat=7.0.80

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:7.0.70-25.ep7.el6
  2. Upgrade

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

    Fixed in 0:8.0.36-29.ep7.el6
  3. Upgrade

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

    Fixed in 0:1.2.8-11.redhat_11.ep7.el6
  4. Upgrade

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

    Fixed in 0:1.1.6-1.Final_redhat_1.1.ep7.el6
  5. Upgrade

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

    Fixed in 0:7.0.70-25.ep7.el7
  6. Upgrade

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

    Fixed in 0:8.0.36-29.ep7.el7
  7. Upgrade

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

    Fixed in 0:1.2.8-11.redhat_11.ep7.el7
  8. Upgrade

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

    Fixed in 0:1.1.6-1.Final_redhat_1.1.ep7.el7
  9. Upgrade

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

    Fixed in 7.0.81
  10. Upgrade

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

    Fixed in 7.0.81Patch Fixed_in_Apache_Tomcat_7.0.81

Event History

Sep 19, 2017
CVE Published
12:00 AM
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionWeakness
Data Sourced
via NVD·01:29 PM
DescriptionSeverityWeaknessAffected Software
Sep 2, 2025
Data Sourced
via Ubuntu·12:06 AM
RemedyDescriptionSeverityAffected Software
Sep 18, 2025
Data Sourced
via Launchpad·12:09 AM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-12616?

CVE-2017-12616 is considered a high severity vulnerability that allows for security constraint bypass and potential disclosure of JSP source code.

2

How do I fix CVE-2017-12616?

To fix CVE-2017-12616, upgrade to Apache Tomcat version 7.0.81 or later.

3

Which versions of Apache Tomcat are affected by CVE-2017-12616?

CVE-2017-12616 affects Apache Tomcat versions 7.0.0 to 7.0.80.

4

What types of attacks can exploit CVE-2017-12616?

CVE-2017-12616 can be exploited through specially crafted requests that bypass security constraints.

5

Is CVE-2017-12616 relevant for production environments using Apache Tomcat?

Yes, CVE-2017-12616 is critical for production environments as it poses a risk of unauthorized access to sensitive data.

Company

Resources

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