CVE-2017-5648: Critical severity Apache Tomcat vulnerability

Published Apr 11, 2017
·
Updated

While investigating bug 60718, it was noticed that some calls to application listeners did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.

Affected versions: 7.0.0 to 7.0.75, 8.0.0.RC1 to 8.0.41, 8.5.0 to 8.5.11

Upstream fixes:

Tomcat 7.x:

https://svn.apache.org/viewvc?view=revision&revision=1785777

Tomcat 8.0.x:

https://svn.apache.org/viewvc?view=revision&revision=1785776

Tomcat 8.5.x:

https://svn.apache.org/viewvc?view=revision&revision=1785775

References:

https://tomcat.apache.org/security-7.html#FixedinApacheTomcat7.0.76 https://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.0.42 https://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.5.12

Other sources

While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.

GitHub

Affected Software

176 affected componentsFixes available
redhat/tomcat<7.0.76
7.0.76
redhat/tomcat<8.0.42
8.0.42
redhat/tomcat<8.5.12
8.5.12
maven/org.apache.tomcat.embed:tomcat-embed-core>=7.0.0<=7.0.75
7.0.76
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.0.0<=8.0.41
8.0.42
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<=8.5.12
8.5.13
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0.M1<=9.0.0.M17
9.0.0.M18
maven/org.apache.tomcat:tomcat-catalina>=7.0.0<=7.0.75
7.0.76
maven/org.apache.tomcat:tomcat-catalina>=8.0.0<=8.0.41
8.0.42
maven/org.apache.tomcat:tomcat-catalina>=8.5.0<=8.5.12
8.5.13
maven/org.apache.tomcat:tomcat-catalina>=9.0.0.M1<=9.0.0.M17
9.0.0.M18
Apache Tomcat=7.0.0
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.5
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.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.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=8.0.0
Apache Tomcat=8.0.0-rc1
Apache Tomcat=8.0.1
Apache Tomcat=8.0.2
Apache Tomcat=8.0.3
Apache Tomcat=8.0.4
Apache Tomcat=8.0.5
Apache Tomcat=8.0.6
Apache Tomcat=8.0.7
Apache Tomcat=8.0.8
Apache Tomcat=8.0.9
Apache Tomcat=8.0.10
Apache Tomcat=8.0.11
Apache Tomcat=8.0.12
Apache Tomcat=8.0.13
Apache Tomcat=8.0.14
Apache Tomcat=8.0.15
Apache Tomcat=8.0.16
Apache Tomcat=8.0.17
Apache Tomcat=8.0.18
Apache Tomcat=8.0.19
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.25
Apache Tomcat=8.0.26
Apache Tomcat=8.0.27
Apache Tomcat=8.0.28
Apache Tomcat=8.0.29
Apache Tomcat=8.0.30
Apache Tomcat=8.0.31
Apache Tomcat=8.0.32
Apache Tomcat=8.0.33
Apache Tomcat=8.0.34
Apache Tomcat=8.0.35
Apache Tomcat=8.0.36
Apache Tomcat=8.0.37
Apache Tomcat=8.0.38
Apache Tomcat=8.0.39
Apache Tomcat=8.0.40
Apache Tomcat=8.0.41
Apache Tomcat=8.5.0
Apache Tomcat=8.5.1
Apache Tomcat=8.5.2
Apache Tomcat=8.5.3
Apache Tomcat=8.5.4
Apache Tomcat=8.5.5
Apache Tomcat=8.5.6
Apache Tomcat=8.5.7
Apache Tomcat=8.5.8
Apache Tomcat=8.5.9
Apache Tomcat=8.5.10
Apache Tomcat=8.5.11
Apache Tomcat=9.0.0-milestone1
Apache Tomcat=9.0.0-milestone10
Apache Tomcat=9.0.0-milestone11
Apache Tomcat=9.0.0-milestone12
Apache Tomcat=9.0.0-milestone13
Apache Tomcat=9.0.0-milestone14
Apache Tomcat=9.0.0-milestone15
Apache Tomcat=9.0.0-milestone16
Apache Tomcat=9.0.0-milestone17
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
Apache Tomcat=9.0.0-m1
Apache Tomcat=9.0.0-m10
Apache Tomcat=9.0.0-m11
Apache Tomcat=9.0.0-m12
Apache Tomcat=9.0.0-m13
Apache Tomcat=9.0.0-m14
Apache Tomcat=9.0.0-m15
Apache Tomcat=9.0.0-m16
Apache Tomcat=9.0.0-m17
Apache Tomcat=9.0.0-m2
Apache Tomcat=9.0.0-m3
Apache Tomcat=9.0.0-m4
Apache Tomcat=9.0.0-m5
Apache Tomcat=9.0.0-m6
Apache Tomcat=9.0.0-m7
Apache Tomcat=9.0.0-m8
Apache Tomcat=9.0.0-m9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 7.0.76
  2. Upgrade

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

    Fixed in 8.0.42
  3. Upgrade

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

    Fixed in 8.5.12
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 7.0.76
  5. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.0.42
  6. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.13
  7. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.0.M18
  8. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 7.0.76
  9. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 8.0.42
  10. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 8.5.13
  11. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 9.0.0.M18
  12. Upgrade

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

    Fixed in 7.0.76
  13. Upgrade

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

    Fixed in 8.0.42
  14. Upgrade

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

    Fixed in 8.5.12

Event History

Apr 11, 2017
Data Sourced
via Red Hat·12:57 PM
DescriptionSeverityAffected Software
Apr 17, 2017
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness
Data Sourced
via NVD·04:59 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2022
Advisory Published
via GitHub·01:25 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-5648?

CVE-2017-5648 has a CVSS base score of 5.4, indicating a medium severity vulnerability.

2

How do I fix CVE-2017-5648?

To fix CVE-2017-5648, upgrade to Apache Tomcat versions 7.0.76, 8.0.42, 8.5.12, or 9.0.0.M18 or later.

3

What versions of Apache Tomcat are affected by CVE-2017-5648?

CVE-2017-5648 affects Apache Tomcat versions 7.0.0 to 7.0.75, 8.0.0 to 8.0.41, 8.5.0 to 8.5.11, and 9.0.0.M1 to 9.0.0.M17.

4

What is the nature of the vulnerability in CVE-2017-5648?

The vulnerability in CVE-2017-5648 arises from improper handling of certain calls to application listeners under a SecurityManager.

5

Is CVE-2017-5648 a local or remote vulnerability?

CVE-2017-5648 can be exploited locally when running untrusted applications under a SecurityManager.

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