dbcve.org
TomcatWeb server / proxy · Apache

CVE-2024-52317

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 9.0.96 / 10.1.31 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect object re-cycling and re-use vulnerability in Apache Tomcat. Incorrect recycling of the request and response used by HTTP/2 requests could lead to request and/or response mix-up between users. This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.0-M26, from 10.1.27 through 10.1.30, from 9.0.92 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability in Apache Tomcat's HTTP/2 implementation allows incorrect recycling of request and response objects, potentially causing data from one user's HTTP/2 request to be exposed to another user. This represents a cross-user information disclosure with medium severity (CVSS 6.5).

MitigationUpgrade Apache Tomcat to version 9.0.96, 10.1.31, or 11.0.0. If immediate upgrade is not feasible, disable HTTP/2 protocol support as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 9.0.92, < 9.0.96>= 10.1.27, < 10.1.31= 11.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Tomcat installation directory
    Locate the CATALINA_HOME environment variable or the directory containing Tomcat. Common paths include /opt/tomcat, /usr/share/tomcat, or C:\Program Files\Apache\Tomcat on Windows.
    Affected if Unable to locate Tomcat installation directory prevents version checking.
  2. Determine installed Tomcat version
    Run the version.sh (Linux/Mac) or version.bat (Windows) script in the bin directory, or read the RELEASE-NOTES file in the Tomcat home directory. The output displays the exact version number.
    Affected if Installed version matches affected ranges: 9.0.92 through 9.0.95, 10.1.27 through 10.1.30, or exactly 11.0.0.
  3. Confirm HTTP/2 protocol support is enabled
    Examine the server.xml configuration file in the conf directory. Look for Connector elements that specify protocol="org.apache.coyote.http2.Http2Protocol" or an upgrade protocol (protocol="HTTP/1.1" with upgradeProtocol set to Http2Protocol).
    Affected if HTTP/2 protocol is actively configured on at least one Connector. The vulnerability only applies when HTTP/2 is enabled.
  4. Verify Java runtime supports HTTP/2
    Check that the JRE/JDK version meets Tomcat HTTP/2 requirements (typically Java 7 or later for HTTP/2, though Tomcat 9+ may require Java 8+). Run java -version to confirm.
    Affected if Java runtime is insufficient for HTTP/2, which would mean the feature is effectively unavailable regardless of configuration.

You are affected if your Tomcat version falls within 9.0.92-9.0.95, 10.1.27-10.1.30, or 11.0.0 AND HTTP/2 protocol is explicitly configured and operational on one or more connectors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.96 / 10.1.31 or later
Fixed in 9.0.9610.1.31
Interim mitigation

Upgrade Apache Tomcat to version 9.0.96, 10.1.31, or 11.0.0. If immediate upgrade is not feasible, disable HTTP/2 protocol support as a temporary workaround.

Recommended fix High confidence

9.0.96 (for 9.x), 10.1.31 (for 10.1.x), or 11.0.0 (for 11.x)

  1. 1. Identify the currently running Apache Tomcat version using the bin/version.sh (Unix) or bin\version.bat (Windows) script, or by checking the server startup logs
  2. 2. If running a vulnerable version (9.0.92-9.0.95, 10.1.27-10.1.30, or 11.0.0-M23 to 11.0.0-M26), plan for an upgrade
  3. 3. Download the corresponding fixed Tomcat release: 9.0.96 for 9.x, 10.1.31 for 10.1.x, or 11.0.0 for 11.x from the Apache Tomcat downloads page (https://tomcat.apache.org/)
  4. 4. Back up the existing Tomcat installation, including all configuration files in the conf directory and deployed applications in the webapps directory
  5. 5. Stop the running Tomcat service or process
  6. 6. Replace the Tomcat installation files with the new version, preserving custom configurations from the conf directory
  7. 7. Restart the Tomcat service or process
  8. 8. Verify the upgrade by checking that the version.sh/version.bat script reports the expected new version and that applications function correctly
Caveat Review release notes for any changes in default behavior, API changes, or deprecated features between your current and target version; test applications in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52317 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data