CVE-2023-46589: Apache Tomcat Improper Input Validation vulnerability

CVE-2023-46589 · Severity: high · CVSS 7.5 · Published 2023-11-28

Improper Input Validation vulnerability in Apache Tomcat. Tomcat from 11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.1.15, from 9.0.0-M1 through 9.0.82, and from 8.5.0 through 8.5.95 did not correctly parse HTTP trailer headers. A trailer header that exceeded the header size limit could cause Tomcat to treat a single request as multiple requests leading to the possibility of request smuggling when behind a reverse proxy. Older, EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.0-M11 onwards, 10.1.16 onwards, 9.0.83 onwards or 8.5.96 onwards, which fix the issue.

Technologies: org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2023-46589 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-46589 being exploited in the wild.
How severe is CVE-2023-46589?
High severity, with a CVSS score of 7.5, published 28 November 2023.
Which products and versions are affected?
org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11; org.apache.tomcat:tomcat-coyote (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11.
Is there a fix for CVE-2023-46589?
Yes. org.apache.tomcat:tomcat-catalina (Maven): upgrade to 11.0.0-M11 or later; org.apache.tomcat:tomcat-coyote (Maven): upgrade to 11.0.0-M11 or later; org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.0-M11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-46589?
Check whether you run org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat:tomcat-coyote (Maven) or org.apache.tomcat.embed:tomcat-embed-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.tomcat:tomcat-catalina (Maven): upgrade to 11.0.0-M11 or later
    # set org.apache.tomcat:tomcat-catalina to 11.0.0-M11 in your pom.xml or build.gradle
  • org.apache.tomcat:tomcat-coyote (Maven): upgrade to 11.0.0-M11 or later
    # set org.apache.tomcat:tomcat-coyote to 11.0.0-M11 in your pom.xml or build.gradle
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.0-M11 or later
    # set org.apache.tomcat.embed:tomcat-embed-core to 11.0.0-M11 in your pom.xml or build.gradle

Affected products

  • org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11
  • org.apache.tomcat:tomcat-coyote (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11
  • org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.0-M11

Identifiers

  • CVE-2023-46589
  • GHSA-fccv-jmmp-qg76

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.