Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-50379: CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition in Apache Software Foundation Apache Tomcat

0
Critical
VulnerabilityCVE-2024-50379cvecve-2024-50379cwe-367
Published: Tue Dec 17 2024 (12/17/2024, 12:34:54 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Tomcat

Description

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.

AI-Powered Analysis

AILast updated: 10/29/2025, 12:20:05 UTC

Technical Analysis

CVE-2024-50379 is a critical vulnerability identified in Apache Tomcat, a widely used Java servlet container. The flaw is a Time-of-check Time-of-use (TOCTOU) race condition occurring during the compilation of JavaServer Pages (JSP). Specifically, when the default servlet is configured to allow write operations—a non-default and less common configuration—an attacker can exploit the timing window between the check of a file and its use on case-insensitive file systems. This race condition enables remote code execution (RCE) without requiring authentication or user interaction. The vulnerability affects Apache Tomcat versions from 8.5.0 through 11.0.1, including multiple milestone and release versions. The issue is particularly dangerous because it allows attackers to execute arbitrary code on the server, potentially leading to full system compromise. The vulnerability has been assigned a CVSS v3.1 score of 9.8, reflecting its critical nature with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The Apache Software Foundation has released fixed versions 11.0.2, 10.1.34, and 9.0.98 to address the issue. Although no active exploits have been reported, the vulnerability's characteristics make it a prime target for attackers once weaponized. The root cause lies in the TOCTOU race condition during JSP compilation on case-insensitive file systems, which are common in Windows environments. This makes systems running Tomcat on Windows or similarly case-insensitive platforms particularly vulnerable if the default servlet is misconfigured to allow writes. The vulnerability underscores the importance of secure servlet configuration and timely patching in Java web application environments.

Potential Impact

For European organizations, the impact of CVE-2024-50379 is significant due to the widespread use of Apache Tomcat in enterprise web applications, government services, and critical infrastructure. Successful exploitation can lead to remote code execution, allowing attackers to gain full control over affected servers. This compromises confidentiality by exposing sensitive data, integrity by enabling unauthorized changes, and availability by potentially disrupting services. Organizations running Tomcat on Windows or other case-insensitive file systems with write-enabled default servlets are at highest risk. The vulnerability could be leveraged to deploy ransomware, steal data, or pivot within networks, severely impacting business continuity and regulatory compliance, especially under GDPR. Given the critical severity and ease of exploitation, the threat could lead to large-scale breaches if not promptly mitigated. The lack of required authentication or user interaction lowers the barrier for attackers, increasing the likelihood of exploitation in unpatched environments.

Mitigation Recommendations

1. Immediately upgrade Apache Tomcat to the fixed versions: 11.0.2, 10.1.34, or 9.0.98. 2. Review and disable write permissions on the default servlet unless absolutely necessary, as this non-default configuration enables the vulnerability. 3. For environments that must allow write access, implement strict access controls and monitor for suspicious file operations during JSP compilation. 4. Conduct thorough audits of Tomcat configurations across all servers, especially those running on Windows or other case-insensitive file systems. 5. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules targeting suspicious JSP compilation or file system race conditions. 6. Monitor logs for unusual activity related to JSP compilation or file writes to detect potential exploitation attempts. 7. Isolate critical Tomcat servers within segmented network zones to limit lateral movement if compromised. 8. Educate system administrators about the risks of enabling write access on default servlets and the importance of timely patching. 9. Implement robust backup and recovery procedures to mitigate impact in case of successful exploitation. 10. Stay informed on any emerging exploit reports or additional patches from Apache.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
apache
Date Reserved
2024-10-23T13:31:10.241Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690204553aaa02566521b56f

Added to database: 10/29/2025, 12:11:01 PM

Last enriched: 10/29/2025, 12:20:05 PM

Last updated: 10/30/2025, 4:41:29 PM

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats