Apache Tomcat: RCE due to TOCTOU issue in JSP compilation - CVE-2024-50379 mitigation was incomplete (CVE-2024-56337)
Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0 through 11.0.1, from 10.1.0 through 10.1.33, from 9.0.0 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. The mitigation for CVE-2024-50379 was incomplete. Users running Tomcat on a case insensitive file system with the default servlet write enabled (readonly initialisation parameter set to the non-default value of false) may need additional configuration to fully mitigate CVE-2024-50379 depending on which version of Java they are using with Tomcat: - running on Java 8 or Java 11: the system property sun.io.useCanonCaches must be explicitly set to false (it defaults to true) - running on Java 17: the system property sun.io.useCanonCaches, if set, must be set to false (it defaults to false) - running on Java 21 onwards: no further configuration is required (the system property and the problematic cache have been removed) Tomcat 11.0.3, 10.1.35 and 9.0.99 onwards will include checks that sun.io.useCanonCaches is set appropriately before allowing the default servlet to be write enabled on a case insensitive file system. Tomcat will also set sun.io.useCanonCaches to false by default where it can.
AI Analysis
Technical Summary
This vulnerability is a TOCTOU race condition in Apache Tomcat affecting versions from 11.0.0-M1 through 11.0.1, 10.1.0-M1 through 10.1.33, 9.0.0.M1 through 9.0.97, and 8.5.0 through 8.5.100 (EOL). It arises when Tomcat is run on case insensitive file systems with the default servlet write enabled (readonly initialization parameter set to false). The mitigation for CVE-2024-50379 was incomplete, requiring additional configuration of the Java system property sun.io.useCanonCaches depending on the Java version: set to false explicitly on Java 8 and 11, set to false if set on Java 17, and no action needed on Java 21 and later. Tomcat 11.0.3, 10.1.35, and 9.0.99 and later versions include built-in checks and default the system property to false where applicable to prevent exploitation.
Potential Impact
The vulnerability allows an attacker to exploit a race condition in file handling on case insensitive file systems, potentially leading to full compromise of confidentiality, integrity, and availability of the affected Tomcat server. The CVSS 3.1 vector indicates network exploitable with low complexity, no privileges or user interaction required, and critical impact on all security properties. This could enable remote attackers to execute unauthorized actions or disrupt service.
Mitigation Recommendations
Fixes are available starting with Tomcat versions 11.0.3, 10.1.35, and 9.0.99 which include checks to ensure the system property sun.io.useCanonCaches is set appropriately and default it to false when possible. Users running affected versions should upgrade to these or later versions. For those unable to upgrade immediately, configure the Java system property sun.io.useCanonCaches to false explicitly if running on Java 8 or 11, and ensure it is false if set on Java 17. No additional configuration is required for Java 21 or later. This mitigates the incomplete fix from CVE-2024-50379. Users should verify their default servlet write setting and file system case sensitivity to assess exposure.
Apache Tomcat: RCE due to TOCTOU issue in JSP compilation - CVE-2024-50379 mitigation was incomplete (CVE-2024-56337)
Description
Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0 through 11.0.1, from 10.1.0 through 10.1.33, from 9.0.0 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. The mitigation for CVE-2024-50379 was incomplete. Users running Tomcat on a case insensitive file system with the default servlet write enabled (readonly initialisation parameter set to the non-default value of false) may need additional configuration to fully mitigate CVE-2024-50379 depending on which version of Java they are using with Tomcat: - running on Java 8 or Java 11: the system property sun.io.useCanonCaches must be explicitly set to false (it defaults to true) - running on Java 17: the system property sun.io.useCanonCaches, if set, must be set to false (it defaults to false) - running on Java 21 onwards: no further configuration is required (the system property and the problematic cache have been removed) Tomcat 11.0.3, 10.1.35 and 9.0.99 onwards will include checks that sun.io.useCanonCaches is set appropriately before allowing the default servlet to be write enabled on a case insensitive file system. Tomcat will also set sun.io.useCanonCaches to false by default where it can.
Affected software
pkg:deb/ubuntu/[email protected]+esm2?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/[email protected]~18.04.3+esm6?arch=source&distro=esm-apps/bionicpkg:deb/ubuntu/[email protected]+esm8?arch=source&distro=esm-apps/bionicpkg:deb/ubuntu/[email protected]+esm3?arch=source&distro=esm-apps/focalpkg:deb/ubuntu/[email protected]+esm4?arch=source&distro=esm-apps/jammypkg:deb/ubuntu/[email protected]?arch=source&distro=nobleRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability is a TOCTOU race condition in Apache Tomcat affecting versions from 11.0.0-M1 through 11.0.1, 10.1.0-M1 through 10.1.33, 9.0.0.M1 through 9.0.97, and 8.5.0 through 8.5.100 (EOL). It arises when Tomcat is run on case insensitive file systems with the default servlet write enabled (readonly initialization parameter set to false). The mitigation for CVE-2024-50379 was incomplete, requiring additional configuration of the Java system property sun.io.useCanonCaches depending on the Java version: set to false explicitly on Java 8 and 11, set to false if set on Java 17, and no action needed on Java 21 and later. Tomcat 11.0.3, 10.1.35, and 9.0.99 and later versions include built-in checks and default the system property to false where applicable to prevent exploitation.
Potential Impact
The vulnerability allows an attacker to exploit a race condition in file handling on case insensitive file systems, potentially leading to full compromise of confidentiality, integrity, and availability of the affected Tomcat server. The CVSS 3.1 vector indicates network exploitable with low complexity, no privileges or user interaction required, and critical impact on all security properties. This could enable remote attackers to execute unauthorized actions or disrupt service.
Mitigation Recommendations
Fixes are available starting with Tomcat versions 11.0.3, 10.1.35, and 9.0.99 which include checks to ensure the system property sun.io.useCanonCaches is set appropriately and default it to false when possible. Users running affected versions should upgrade to these or later versions. For those unable to upgrade immediately, configure the Java system property sun.io.useCanonCaches to false explicitly if running on Java 8 or 11, and ensure it is false if set on Java 17. No additional configuration is required for Java 21 or later. This mitigates the incomplete fix from CVE-2024-50379. Users should verify their default servlet write setting and file system case sensitivity to assess exposure.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2024-56337
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:Pro:22.04:LTS","Ubuntu:24.04:LTS"]
- Cvss Version
- 3.1
Threat ID: 6a58b50b68715ace43db2e85
Added to database: 07/16/2026, 10:40:11 UTC
Last enriched: 07/30/2026, 11:28:00 UTC
Last updated: 09/10/2026, 19:36:49 UTC
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.