CVE-2020-11996: High severity IBM Data Risk Manager vulnerability

Published Jun 25, 2020
·
Updated

A specially crafted sequence of HTTP/2 requests could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.

Reference: https://tomcat.apache.org/security-8.html

Other sources

A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.

Apache Tomcat is vulnerable to a denial of service. By sending a specially crafted sequence of HTTP/2 requests, a remote attacker could exploit this vulnerability to trigger high CPU usage for several seconds.

— IBM

Affected Software

63 affected componentsFixes available
redhat/jws5-jboss-logging<0:3.4.1-1.Final_redhat_00001.1.el6
0:3.4.1-1.Final_redhat_00001.1.el6
redhat/jws5-tomcat<0:9.0.36-6.redhat_5.2.el6
0:9.0.36-6.redhat_5.2.el6
redhat/jws5-tomcat-native<0:1.2.25-2.redhat_2.el6
0:1.2.25-2.redhat_2.el6
redhat/jws5-jboss-logging<0:3.4.1-1.Final_redhat_00001.1.el7
0:3.4.1-1.Final_redhat_00001.1.el7
redhat/jws5-tomcat<0:9.0.36-6.redhat_5.2.el7
0:9.0.36-6.redhat_5.2.el7
redhat/jws5-tomcat-native<0:1.2.25-2.redhat_2.el7
0:1.2.25-2.redhat_2.el7
redhat/jws5-jboss-logging<0:3.4.1-1.Final_redhat_00001.1.el8
0:3.4.1-1.Final_redhat_00001.1.el8
redhat/jws5-tomcat<0:9.0.36-6.redhat_5.2.el8
0:9.0.36-6.redhat_5.2.el8
redhat/jws5-tomcat-native<0:1.2.25-2.redhat_2.el8
0:1.2.25-2.redhat_2.el8
maven/org.apache.tomcat:tomcat>=8.5.0<8.5.55
8.5.55
maven/org.apache.tomcat:tomcat>=9.0.0.M1<9.0.35
9.0.35
maven/org.apache.tomcat:tomcat>=10.0.0-M1<=10.0.0-M4
10.0.0-M5
IBM Data Risk Manager<=2.0.6
Apache Tomcat>=8.5.0<=8.5.55
Apache Tomcat>=9.0.0<=9.0.35
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-milestone18
Apache Tomcat=9.0.0-milestone19
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone20
Apache Tomcat=9.0.0-milestone21
Apache Tomcat=9.0.0-milestone22
Apache Tomcat=9.0.0-milestone23
Apache Tomcat=9.0.0-milestone24
Apache Tomcat=9.0.0-milestone25
Apache Tomcat=9.0.0-milestone26
Apache Tomcat=9.0.0-milestone27
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=10.0.0-milestone1
Apache Tomcat=10.0.0-milestone2
Apache Tomcat=10.0.0-milestone3
Apache Tomcat=10.0.0-milestone4
Apache Tomcat=10.0.0-milestone5
Canonical Ubuntu Linux=20.04
Oracle MySQL Enterprise Monitor<=8.0.21
Oracle Siebel UI Framework<=20.12
Oracle Workload Manager=12.2.0.1
Oracle Workload Manager=18c
Oracle Workload Manager=19c
openSUSE Leap=15.1
openSUSE Leap=15.2
Debian Debian Linux=9.0
Debian Debian Linux=10.0
NetApp OnCommand System Manager=3.0
NetApp OnCommand System Manager=3.1.3
redhat/tomcat<10.0.0
10.0.0
redhat/tomcat<9.0.36
9.0.36
redhat/tomcat<8.5.56
8.5.56
debian/tomcat9
9.0.70-29.0.95-19.0.118-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:3.4.1-1.Final_redhat_00001.1.el6
  2. Upgrade

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

    Fixed in 0:9.0.36-6.redhat_5.2.el6
  3. Upgrade

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

    Fixed in 0:1.2.25-2.redhat_2.el6
  4. Upgrade

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

    Fixed in 0:3.4.1-1.Final_redhat_00001.1.el7
  5. Upgrade

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

    Fixed in 0:9.0.36-6.redhat_5.2.el7
  6. Upgrade

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

    Fixed in 0:1.2.25-2.redhat_2.el7
  7. Upgrade

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

    Fixed in 0:3.4.1-1.Final_redhat_00001.1.el8
  8. Upgrade

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

    Fixed in 0:9.0.36-6.redhat_5.2.el8
  9. Upgrade

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

    Fixed in 0:1.2.25-2.redhat_2.el8
  10. Upgrade

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

    Fixed in 8.5.55
  11. Upgrade

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

    Fixed in 9.0.35
  12. Upgrade

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

    Fixed in 10.0.0-M5
  13. Upgrade

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

    Fixed in 10.0.0
  14. Upgrade

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

    Fixed in 9.0.36
  15. Upgrade

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

    Fixed in 8.5.56
  16. Upgrade

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

    Fixed in 9.0.70-2Fixed in 9.0.95-1Fixed in 9.0.118-1

Event History

Jun 25, 2020
CVE Published
12:00 AM
Jun 26, 2020
Data Sourced
via Red Hat·01:31 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·04:27 PM
Data Sourced
via MITRE·04:27 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityAffected Software
Feb 9, 2022
Advisory Published
via GitHub·11:01 PM
Feb 23, 2026
Data Sourced
via Ubuntu·06:47 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·06:48 PM
Description
Sep 2, 2026
Data Sourced
via Debian·05:58 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2020-11996?

CVE-2020-11996 is a vulnerability in Apache Tomcat that could trigger high CPU usage and make the server unresponsive.

2

How does CVE-2020-11996 impact Apache Tomcat?

CVE-2020-11996 can cause high CPU usage in Apache Tomcat and make the server unresponsive.

3

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

Apache Tomcat versions 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35, and 8.5.0 to 8.5.55 are affected by CVE-2020-11996.

4

How severe is CVE-2020-11996?

CVE-2020-11996 has a severity rating of high.

5

Where can I find more information about CVE-2020-11996?

You can find more information about CVE-2020-11996 on the Apache Tomcat website.

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