dbcve.org
TomcatWeb server / proxy · Apache

CVE-2024-50379

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability during JSP compilation in Apache Tomcat permits an RCE on case insensitive file systems when the default servlet is enabled for write (non-default configuration). 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.0.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

A Time-of-check Time-of-use (TOCTOU) race condition exists in Apache Tomcat's JSP compilation process. When the default servlet is configured to allow writes (non-default) and the server runs on a case-insensitive file system (such as Windows or macOS), an attacker can exploit the race window to achieve remote code execution by manipulating JSP files during compilation.

MitigationUpgrade to Apache Tomcat 9.0.98, 10.1.34, or 11.0.2. Alternatively, ensure the default servlet is not enabled for write operations (the default configuration), or deploy on case-sensitive file systems.

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
High
Integrity
High
Availability
High

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

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 version
    Locate the Tomcat installation directory. Check the version by inspecting the VERSION file in the Tomcat home directory, or run the version.sh (or version.bat on Windows) script located in the bin folder. Alternatively, check the MANIFEST.MF file inside the catalina.jar file in the lib directory.
    Affected if The installed version falls within 9.0.0 to 9.0.97 (inclusive), 10.1.0 to 10.1.33 (inclusive), or 11.0.0 to 11.0.1 (inclusive).
  2. Verify default servlet write configuration
    Examine the Tomcat conf/web.xml file. Locate the <servlet> element for the 'default' servlet. Look for an <init-param> with <param-name>readonly</param-name> and check its <param-value>.
    Affected if The readonly parameter is set to false or any value other than true, indicating the default servlet allows write operations.
  3. Determine the file system type
    Identify the operating system hosting the Tomcat instance. On Windows, the file system is case-insensitive by default. On macOS, verify the underlying file system format (APFS by default is case-insensitive unless case-sensitive mode was chosen). On Linux or BSD systems, file systems are typically case-sensitive.
    Affected if The Tomcat instance runs on Windows or macOS with a case-insensitive file system configuration.

A user is affected if their Tomcat version is in the vulnerable range AND the default servlet is configured to allow writes (readonly=false) AND the server runs on a case-insensitive file system (Windows or macOS).

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 to Apache Tomcat 9.0.98, 10.1.34, or 11.0.2. Alternatively, ensure the default servlet is not enabled for write operations (the default configuration), or deploy on case-sensitive file systems.

Recommended fix High confidence

Apache Tomcat 9.0.98, 10.1.34, or 11.0.2 (depending on your current major version line)

  1. 1. Stop the Tomcat service
  2. 2. Create a complete backup of the current Tomcat installation directory
  3. 3. Download the fixed version (9.0.98 for 9.x, 10.1.34 for 10.1.x, or 11.0.2 for 11.x) from the official Apache Tomcat download page
  4. 4. Extract the new Tomcat version to a temporary location
  5. 5. Copy the conf/ directory from the backup to the new installation (preserving custom configurations)
  6. 6. Copy any custom web applications from the old installation to the new one
  7. 7. Start the Tomcat service and verify the version is correct
  8. 8. Test that applications function properly after the upgrade
Caveat Minor Tomcat upgrades typically preserve configuration but review release notes for any deprecation warnings or behavioral changes

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

Fix this in Tomcat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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