CVE-2019-17569: XSS

Published Feb 24, 2020
·
Updated

Apache Tomcat is vulnerable to HTTP request smuggling, caused by a flaw when handling unusual Transfer-Encoding HTTP header. By sending a specially-crafted request, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

Other sources

The refactoring in 9.0.28 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.

It affects the version of Apache Tomcat 9 from 9.0.28 to 9.0.30, Tomcat from 8 8.5.48 to 8.5.50, and Tomcat 7 7.0.98 to 7.0.99.

Upstream Patches: https://github.com/apache/tomcat/commit/060ecc5 / tomcat9 https://github.com/apache/tomcat/commit/959f1df / tomcat8 https://github.com/apache/tomcat/commit/b191a0d / tomcat7

— Red Hat

The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.

Affected Software

39 affected componentsFixes available
redhat/jws5-tomcat<0:9.0.30-3.redhat_4.1.el6
0:9.0.30-3.redhat_4.1.el6
redhat/jws5-tomcat-native<0:1.2.23-4.redhat_4.el6
0:1.2.23-4.redhat_4.el6
redhat/jws5-tomcat<0:9.0.30-3.redhat_4.1.el7
0:9.0.30-3.redhat_4.1.el7
redhat/jws5-tomcat-native<0:1.2.23-4.redhat_4.el7
0:1.2.23-4.redhat_4.el7
redhat/jws5-tomcat<0:9.0.30-3.redhat_4.1.el8
0:9.0.30-3.redhat_4.1.el8
redhat/jws5-tomcat-native<0:1.2.23-4.redhat_4.el8
0:1.2.23-4.redhat_4.el8
debian/tomcat9
9.0.31-1~deb10u69.0.31-1~deb10u109.0.43-2~deb11u69.0.43-2~deb11u99.0.70-2
IBM Data Risk Manager<=2.0.6
Apache Tomcat>=7.0.98<=7.0.99
Apache Tomcat>=8.5.48<=8.5.50
Apache Tomcat>=9.0.28<=9.0.30
Apache TomEE=7.0.7
openSUSE Leap=15.1
NetApp Data Availability Services
NetApp OnCommand System Manager>=3.0.0<=3.1.3
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Oracle Agile Engineering Data Management=6.2.1.0
Oracle Agile PLM=9.3.3
Oracle Agile PLM=9.3.5
Oracle Agile PLM=9.3.6
Oracle Communications Instant Messaging Server=10.0.1.4.0
Oracle Health Sciences Empirica Inspections=1.0.1.2
Oracle Health Sciences Empirica Signal=7.3.3
Oracle Hospitality Guest Access=4.2.0
Oracle Hospitality Guest Access=4.2.1
Oracle Instantis Enterprisetrack>=17.1<=17.3
Oracle MySQL Enterprise Monitor<=4.0.12
Oracle MySQL Enterprise Monitor>=8.0.0<=8.0.20
Oracle Transportation Management=6.3.7
Oracle Workload Manager=12.2.0.1
Oracle Workload Manager=18c
Oracle Workload Manager=19c
redhat/tomcat<9.0.31
9.0.31
redhat/tomcat<8.5.51
8.5.51
redhat/tomcat<7.0.100
7.0.100
Oracle Agile Product Lifecycle Management=9.3.3
Oracle Agile Product Lifecycle Management=9.3.5
Oracle Agile Product Lifecycle Management=9.3.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:9.0.30-3.redhat_4.1.el6
  2. Upgrade

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

    Fixed in 0:1.2.23-4.redhat_4.el6
  3. Upgrade

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

    Fixed in 0:9.0.30-3.redhat_4.1.el7
  4. Upgrade

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

    Fixed in 0:1.2.23-4.redhat_4.el7
  5. Upgrade

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

    Fixed in 0:9.0.30-3.redhat_4.1.el8
  6. Upgrade

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

    Fixed in 0:1.2.23-4.redhat_4.el8
  7. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.31-1~deb10u6Fixed in 9.0.31-1~deb10u10Fixed in 9.0.43-2~deb11u6Fixed in 9.0.43-2~deb11u9Fixed in 9.0.70-2
  8. Upgrade

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

    Fixed in 9.0.31
  9. Upgrade

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

    Fixed in 8.5.51
  10. Upgrade

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

    Fixed in 7.0.100
  11. Upgrade

    Upgrade apache/tomcat/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.30Patch 060ecc5
  12. Upgrade

    Upgrade apache/tomcat/tomcat8 to a version that resolves this vulnerability.

    Fixed in 8.5.50Patch 959f1df
  13. Upgrade

    Upgrade apache/tomcat/tomcat7 to a version that resolves this vulnerability.

    Fixed in 7.0.99Patch b191a0d
  14. Compensating control

    If Apache Tomcat is located behind a reverse proxy, ensure the reverse proxy does not incorrectly handle invalid Transfer-Encoding headers in a way that could enable HTTP request smuggling.

Event History

Feb 24, 2020
CVE Published
12:00 AM
CVE Published
via MITRE·09:04 PM
Data Sourced
via MITRE·09:04 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 25, 2020
Data Sourced
via Red Hat·07:13 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2019-17569?

CVE-2019-17569 is a vulnerability in Apache Tomcat that allows for HTTP request smuggling.

2

How severe is CVE-2019-17569?

CVE-2019-17569 has a severity rating of 6.5, which is considered medium.

3

What software versions are affected by CVE-2019-17569?

Apache Tomcat versions 9.0.28 to 9.0.30, 8.5.48 to 8.5.50, and 7.0.98 to 7.0.99 are affected by CVE-2019-17569.

4

How can I fix CVE-2019-17569?

To fix CVE-2019-17569, you should update Apache Tomcat to version 9.0.31, 8.5.51, or 7.0.100.

5

Where can I find more information about CVE-2019-17569?

You can find more information about CVE-2019-17569 on the Apache Tomcat GitHub page.

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