dbcve.org
TomcatWeb server / proxy · Apache

CVE-2024-54677

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-17
Fix available
A fix is available. Upgrade to 9.0.98 / 10.1.34 or later.
See remediation →
62/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
Uncontrolled Resource Consumption vulnerability in the examples web application provided with Apache Tomcat leads to denial of service. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.1, from 10.1.0-M1 through 10.1.33, from 9.0.0.M1 through 9.9.97. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.2, 10.1.34 or 9.0.98, 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

Uncontrolled resource consumption in the examples web application bundled with Apache Tomcat allows remote attackers to cause denial of service by exhausting server resources. The vulnerability exists specifically in the examples application, not the Tomcat core itself.

MitigationUpgrade Apache Tomcat to version 11.0.2, 10.1.34, or 9.0.98. Alternatively, remove or disable the examples web application (located in $CATALINA_HOME/webapps/examples) as a mitigation if upgrading is not immediately feasible.

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.0, < 9.0.98>= 10.1.0, < 10.1.34>= 11.0.0, < 11.0.2
Bootstrap OsOperating system
Affected:all versions

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
None
Integrity
None
Availability
Low

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

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. Check if the examples web application is deployed
    Inspect the $CATALINA_HOME/webapps directory for the presence of the examples folder, or check the web.xml and conf/Catalina/localhost/ for examples context configuration
    Affected if The examples folder exists in webapps or the examples context is loaded in Tomcat
  2. Identify the installed Apache Tomcat version
    Check the RELEASE-NOTE file in the Tomcat installation directory, or run: catalina.sh version (Unix) or catalina.bat version (Windows)
    Affected if The version number cannot be determined or is not visible in standard version files
  3. Compare installed version against affected ranges
    Review the version output and compare numerically against: 9.0.0 to 9.0.97, 10.1.0 to 10.1.33, or 11.0.0 to 11.0.1
    Affected if The installed version falls within any of the affected ranges: 9.0.0 <= version < 9.0.98, 10.1.0 <= version < 10.1.34, or 11.0.0 <= version < 11.0.2

A user is affected if they are running a vulnerable Tomcat version (9.0.0-9.0.97, 10.1.0-10.1.33, or 11.0.0-11.0.1) AND the examples web application is deployed in their webapps directory.

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.98 / 10.1.34 / 11.0.2 or later
Fixed in 9.0.9810.1.3411.0.2
Interim mitigation

Upgrade Apache Tomcat to version 11.0.2, 10.1.34, or 9.0.98. Alternatively, remove or disable the examples web application (located in $CATALINA_HOME/webapps/examples) as a mitigation if upgrading is not immediately feasible.

Recommended fix High confidence

9.0.98 (for 9.x) | 10.1.34 (for 10.1.x) | 11.0.2 (for 11.x)

  1. 1. Stop the Apache Tomcat server gracefully
  2. 2. Backup the existing Tomcat installation directory and all configuration files
  3. 3. Download the appropriate fixed version (9.0.98 for Tomcat 9.x, 10.1.34 for Tomcat 10.1.x, or 11.0.2 for Tomcat 11.x) from the official Apache Tomcat downloads page (tomcat.apache.org)
  4. 4. Extract the new Tomcat version to a temporary location
  5. 5. Copy the conf directory from your backup to the new installation to preserve custom configurations
  6. 6. Deploy your web applications to the new Tomcat installation
  7. 7. Start the Tomcat server and verify the examples web application is no longer accessible or has been updated
  8. 8. Monitor application logs for any errors
Caveat Minimal risk - patch releases typically contain only bug/security fixes; review the Tomcat changelog for any behavior changes

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54677 — 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-54677 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