medium
6.5
CWE
79 444
Advisory Published
CVE Published
Updated

CVE-2020-1935: XSS

First published: Mon Feb 24 2020(Updated: )

A flaw was found in Apache Tomcat. The HTTP header parsing code used an approach to end-of-line (EOL) parsing that allowed some invalid HTTP headers to be parsed as valid. This led to the 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. The highest threat with this vulnerability is system availability.

Credit: security@apache.org

Affected SoftwareAffected VersionHow to fix
redhat/tomcat<0:7.0.76-16.el7_9
0:7.0.76-16.el7_9
redhat/tomcat<0:7.0.76-11.el7_6
0:7.0.76-11.el7_6
redhat/tomcat<0:7.0.76-12.el7_7
0:7.0.76-12.el7_7
redhat/tomcat7<0:7.0.70-41.ep7.el6
0:7.0.70-41.ep7.el6
redhat/tomcat8<0:8.0.36-45.ep7.el6
0:8.0.36-45.ep7.el6
redhat/tomcat7<0:7.0.70-41.ep7.el7
0:7.0.70-41.ep7.el7
redhat/tomcat8<0:8.0.36-45.ep7.el7
0:8.0.36-45.ep7.el7
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
redhat/tomcat<9.0.31
9.0.31
redhat/tomcat<8.5.51
8.5.51
redhat/tomcat<7.0.100
7.0.100
debian/tomcat9
9.0.43-2~deb11u10
9.0.43-2~deb11u11
9.0.70-2
9.0.95-1
IBM Data Risk Manager<=2.0.6
Tomcat>=7.0.0<=7.0.99
Tomcat>=8.5.0<=8.5.50
Tomcat>=9.0.0<=9.0.30
Tomcat=9.0.0
Tomcat=9.0.0-milestone1
Tomcat=9.0.0-milestone10
Tomcat=9.0.0-milestone11
Tomcat=9.0.0-milestone12
Tomcat=9.0.0-milestone13
Tomcat=9.0.0-milestone14
Tomcat=9.0.0-milestone15
Tomcat=9.0.0-milestone16
Tomcat=9.0.0-milestone17
Tomcat=9.0.0-milestone18
Tomcat=9.0.0-milestone19
Tomcat=9.0.0-milestone2
Tomcat=9.0.0-milestone20
Tomcat=9.0.0-milestone21
Tomcat=9.0.0-milestone22
Tomcat=9.0.0-milestone23
Tomcat=9.0.0-milestone24
Tomcat=9.0.0-milestone25
Tomcat=9.0.0-milestone26
Tomcat=9.0.0-milestone27
Tomcat=9.0.0-milestone3
Tomcat=9.0.0-milestone4
Tomcat=9.0.0-milestone5
Tomcat=9.0.0-milestone6
Tomcat=9.0.0-milestone7
Tomcat=9.0.0-milestone8
Tomcat=9.0.0-milestone9
Debian=8.0
Debian=9.0
Debian=10.0
Ubuntu=16.04
SUSE Linux=15.1
NetApp Data Availability Services
NetApp System Manager>=3.0.0<=3.1.3
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 Element Manager=8.1.1
Oracle Communications Element Manager=8.2.0
Oracle Communications Element Manager=8.2.1
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 Hyperion Infrastructure Technology=11.1.2.4
Oracle Instantis EnterpriseTrack>=17.1<=17.3
MySQL Enterprise Monitor>=4.0.0<=4.0.12
MySQL Enterprise Monitor>=8.0.0<=8.0.20
Oracle Retail Order Broker=15.0
Oracle Siebel User Interface Framework<=20.5
Oracle Transportation Execution=6.3.7
Oracle Workload Manager=12.2.0.1
Oracle Workload Manager=18c
Oracle Workload Manager=19c

Remedy

Workaround for Red Hat Satellite 6 is to add iptables rule to deny TCP requests of Tomcat that are not originating from the Satellite. For other Red Hat products, either mitigation isn't available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2020-1935?

    CVE-2020-1935 has a moderate severity level due to the potential for HTTP request smuggling.

  • How do I fix CVE-2020-1935?

    To fix CVE-2020-1935, upgrade to Apache Tomcat version 7.0.100, 8.5.51, or 9.0.31 or later.

  • Which versions of Apache Tomcat are affected by CVE-2020-1935?

    CVE-2020-1935 affects Apache Tomcat versions before 7.0.100, 8.5.51, and 9.0.31.

  • What is HTTP request smuggling related to CVE-2020-1935?

    HTTP request smuggling involves sending maliciously crafted requests that can bypass security controls by exploiting the flawed header parsing.

  • Is CVE-2020-1935 applicable to reverse proxy configurations?

    Yes, CVE-2020-1935 is particularly concerning when Tomcat is deployed behind a reverse proxy that does not handle headers correctly.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203