CVE-2024-24549: Apache Tomcat: HTTP/2 header handling DoS

Published Mar 13, 2024
·
Updated

Denial of Service due to improper input validation vulnerability for HTTP/2 requests in Apache Tomcat. When processing an HTTP/2 request, if the request exceeded any of the configured limits for headers, the associated HTTP/2 stream was not reset until after all of the headers had been processed.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98.

Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.

Other sources

Denial of Service due to improper input validation vulnerability for HTTP/2 requests in Apache Tomcat. When processing an HTTP/2 request, if the request exceeded any of the configured limits for headers, the associated HTTP/2 stream was not reset until after all of the headers had been processed.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98. Other, older, EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.

— MITRE

Affected Software

35 affected componentsFixes available
maven/org.apache.tomcat:tomcat-coyote>=8.5.0<=8.5.98
8.5.99
maven/org.apache.tomcat:tomcat-coyote>=9.0.0-M1<=9.0.85
9.0.86
maven/org.apache.tomcat:tomcat-coyote>=10.1.0-M1<=10.1.18
10.1.19
maven/org.apache.tomcat:tomcat-coyote>=11.0.0-M1<=11.0.0-M16
11.0.0-M17
maven/org.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1<=11.0.0-M16
11.0.0-M17
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<=10.1.18
10.1.19
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0-M1<=9.0.85
9.0.86
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<=8.5.98
8.5.99
redhat/Apache Tomcat<11.0.0
11.0.0
redhat/Apache Tomcat<10.1.19
10.1.19
redhat/Apache Tomcat<9.0.86
9.0.86
redhat/Apache Tomcat<8.5.99
8.5.99
Apache Tomcat>=8.5.0<8.5.99
Apache Tomcat>=9.0.0<9.0.86
Apache Tomcat>=10.1.0<10.1.19
Apache Tomcat=11.0.0-milestone1
Apache Tomcat=11.0.0-milestone10
Apache Tomcat=11.0.0-milestone11
Apache Tomcat=11.0.0-milestone12
Apache Tomcat=11.0.0-milestone13
Apache Tomcat=11.0.0-milestone14
Apache Tomcat=11.0.0-milestone15
Apache Tomcat=11.0.0-milestone16
Apache Tomcat=11.0.0-milestone2
Apache Tomcat=11.0.0-milestone3
Apache Tomcat=11.0.0-milestone4
Apache Tomcat=11.0.0-milestone5
Apache Tomcat=11.0.0-milestone6
Apache Tomcat=11.0.0-milestone7
Apache Tomcat=11.0.0-milestone8
Apache Tomcat=11.0.0-milestone9
Debian Debian Linux=10.0
Fedoraproject Fedora=39
Fedoraproject Fedora=40
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 8.5.99
  2. Upgrade

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

    Fixed in 9.0.86
  3. Upgrade

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

    Fixed in 10.1.19
  4. Upgrade

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

    Fixed in 11.0.0-M17
  5. Upgrade

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

    Fixed in 11.0.0-M17
  6. Upgrade

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

    Fixed in 10.1.19
  7. Upgrade

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

    Fixed in 9.0.86
  8. Upgrade

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

    Fixed in 8.5.99
  9. Upgrade

    Upgrade redhat/Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.0
  10. Upgrade

    Upgrade redhat/Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.19
  11. Upgrade

    Upgrade redhat/Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.86
  12. Upgrade

    Upgrade redhat/Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.99
  13. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.0-M17
  14. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.19
  15. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.86
  16. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.99

Event History

Mar 13, 2024
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
Affected Software
Advisory Published
via GitHub·06:31 PM
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2024-24549?

CVE-2024-24549 has a severity rating of medium due to its potential to cause denial of service.

2

How do I fix CVE-2024-24549?

To fix CVE-2024-24549, upgrade Apache Tomcat to version 8.5.99, 9.0.86, 10.1.19, or 11.0.0-M17, depending on your version.

3

What systems are affected by CVE-2024-24549?

CVE-2024-24549 affects multiple versions of Apache Tomcat, specifically those prior to 8.5.99, 9.0.86, 10.1.19, and 11.0.0-M17.

4

Is there a workaround for CVE-2024-24549?

Currently, the recommendation is to apply the available patches rather than relying on workarounds for CVE-2024-24549.

5

What type of attack does CVE-2024-24549 allow?

CVE-2024-24549 allows remote attackers to perform denial of service attacks by sending specially crafted HTTP/2 requests.

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