Critical Flaws Put Apache Tomcat Servers at Risk

TL;DR: Critical vulnerabilities in Apache Tomcat could let attackers crash servers or even run their own code. The flaws affect how the popular web server handles certain web requests, putting many applications at risk of downtime.
Key facts
- Category
- Cybersecurity
- Impact
- Critical
- Published
- Source
- Ubuntu Security Notices
Full summary
Newly found flaws in the popular Apache Tomcat web server could let remote attackers crash systems or potentially run malicious code.
Security researchers have uncovered critical vulnerabilities in Apache Tomcat, a widely used Java web server, putting countless applications at risk. The advisory highlights two major flaws that can be exploited by remote attackers. The first vulnerability involves how Tomcat handles certain web requests (WebDAV LOCK and PROPFIND). The server fails to limit the size of these requests, allowing an attacker to send an oversized request that consumes excessive memory. This can easily lead to a denial-of-service (DoS) attack, causing the server to slow down or crash completely. A second, more severe flaw was discovered in Tomcat's processing of HTTP/2 header fields. The software does not validate these headers correctly, creating an opening for a malicious request to crash the server. Worryingly, security experts note this particular vulnerability could potentially be used to achieve remote code execution (RCE), which would allow an attacker to take full control of the affected system.
These vulnerabilities are a serious concern for any organization using Apache Tomcat. A DoS attack can cause significant downtime, disrupting services and damaging a company's reputation. The threat of remote code execution is even greater, as a successful exploit could lead to data breaches, malware installation, or the compromised server being used to attack other internal systems. Given Tomcat's popularity in enterprise environments, the potential impact is vast, affecting developers, IT administrators, and security teams who manage these servers. Immediate action is required to mitigate the risk. System administrators must identify all running instances of Apache Tomcat within their infrastructure and apply the necessary security patches as soon as possible. Delaying these updates leaves servers exposed to automated attacks that actively scan the internet for unpatched and vulnerable systems, making swift remediation a top priority for protecting business-critical applications.
Why it matters
These flaws expose a widely used web server to severe risks, including complete server takeover (RCE) and forced downtime (DoS). Because Tomcat is a foundational component for many Java applications, a compromise could lead to significant data breaches or service interruptions.
Business impact
A successful exploit could lead to costly downtime, loss of customer trust, and potential data theft, triggering regulatory fines and reputational damage. The RCE vulnerability is particularly severe, as it could give attackers a foothold into the corporate network.
⚡ Action needed
Immediate patching is required for all affected Apache Tomcat installations.
Action checklist
- 1Identify all Apache Tomcat instances in your environment.
- 2Check your current Tomcat version against the advisory.
- 3Apply the latest security patches provided by your vendor.
- 4Monitor systems for any unusual activity after patching.
- 5Review security configurations for HTTP/2 and WebDAV.
Tags
Related on Notifire
Primary source: Ubuntu Security Notices