Tuesday, March 11, 2025
HomeCVE/vulnerabilityApache Tomcat Flaw Could Allow RCE Attacks on Servers

Apache Tomcat Flaw Could Allow RCE Attacks on Servers

Published on

SIEM as a Service

Follow Us on Google News

Apache Tomcat, a widely used open-source web server software, has faced numerous security vulnerabilities in recent years.

Some critical issues put servers at risk of remote code execution (RCE) and other attacks.

These vulnerabilities highlight the importance of keeping software up-to-date and properly configured to prevent potential exploits.

Detailed Vulnerabilities:

Below is a formatted table summarizing the CVEs mentioned in the Apache Tomcat vulnerabilities:

CVEVulnerability TypeDescriptionAffected Versions
CVE-2025-24813Remote Code Execution and Information DisclosureTemporary file vulnerability in partial PUT operations allowing access to security-sensitive files and potential RCE with certain conditions.11.0.0-M1 to 11.0.2
CVE-2024-56337Remote Code ExecutionIncomplete mitigation for CVE-2024-50379, requiring additional configuration on case-insensitive file systems.11.0.0-M1 to 11.0.1
CVE-2024-54677Denial of ServiceOutOfMemoryError in examples web app due to unlimited uploaded data.11.0.0-M1 to 11.0.1
CVE-2024-50379Remote Code ExecutionRCE via write-enabled default servlet on case-insensitive file systems.11.0.0-M1 to 11.0.1
CVE-2024-52318Cross-Site Scripting (XSS)Unescaped output from pooled JSP tags could lead to XSS.11.0.0
CVE-2024-52317Request and Response Mix-upIncorrectly recycled HTTP/2 requests could lead to data mix-ups between users.11.0.0-M23 to 11.0.0-M26
CVE-2024-52316Authentication BypassPotential bypass if custom authentication components throw exceptions without setting failure status.11.0.0-M1 to 11.0.0-M26
CVE-2024-38286Denial of ServiceOutOfMemoryError triggered by abusing the TLS handshake process.11.0.0-M1 to 11.0.0-M20
CVE-2024-34750Denial of ServiceIncorrect handling of HTTP/2 streams led to miscounting active streams.11.0.0-M1 to 11.0.0-M20
CVE-2024-23672Denial of ServiceWebSocket clients could keep connections open for resource exhaustion.11.0.0-M1 to 11.0.0-M16
CVE-2024-24549Denial of ServiceFailure to reset HTTP/2 streams after exceeding header limits.11.0.0-M1 to 11.0.0-M16
CVE-2023-45648Request SmugglingIncorrect parsing of HTTP trailer headers could lead to request smuggling.11.0.0-M1 to 11.0.0-M11
CVE-2023-44487Denial of ServiceRapid reset attack could cause OutOfMemoryError via HTTP/2 implementation.11.0.0-M1 to 11.0.0-M11
CVE-2023-42795Information DisclosureIncomplete request/response recycling could lead to information leaks.11.0.0-M1 to 11.0.0-M11
CVE-2023-41080Open RedirectSpecially crafted URLs could trigger redirects under certain conditions.11.0.0-M1 to 11.0.0-M10
CVE-2023-46589Request SmugglingTrailer headers exceeding size limits could cause request smuggling.11.0.0-M1 to 11.0.0-M10
CVE-2023-34981Information DisclosureRegression in AJP SEND_HEADERS message processing could leak headers.11.0.0-M5
CVE-2023-28709Denial of ServiceIncomplete fix for previous DoS vulnerability, affecting query string parameters.11.0.0-M2 to 11.0.0-M4
CVE-2023-28708Information DisclosureSession cookies lacked secure attribute when using RemoteIpFilter.11.0.0-M1 to 11.0.0-M2
CVE-2023-24998Denial of ServiceUnrestricted file upload parts could lead to resource exhaustion.11.0.0-M1

Steps to Mitigate Risks:

  • Upgrade Software: Ensure Apache Tomcat and related software are upgraded to the latest versions to apply security patches for known vulnerabilities.
  • Disable Default Servlet Writes: By default, writes to the default servlet are disabled. Ensure this setting remains unchanged unless necessary for specific applications.
  • Proper Configuration: Regularly review configuration files to ensure they adhere to best practices, limiting potential attack vectors.
  • Monitor System Resources: Keep an eye on system resources to quickly identify and address anomalies that might indicate a denial of service attack.
  • Regular Audits and Testing: Conduct periodic security audits and penetration testing to identify any misconfigurations or vulnerabilities before they can be exploited.

The ongoing series of vulnerabilities in Apache Tomcat underscores the importance of maintaining robust security measures and staying up-to-date with the latest software updates.

While many of these issues are mitigated through updates, understanding the nature of these vulnerabilities helps administrators better secure their servers against potential threats.

Continuous monitoring and maintenance are crucial in protecting servers from both known and emerging risks.

Are you from SOC/DFIR Teams? – Analyse Malware Incidents & get live Access with ANY.RUN -> Start Now for Free.

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Threat Actors Evade Security Measures to Launch SIM Swap Attacks

SIM swapping fraud continues to pose a significant threat to individuals and financial institutions,...

Ebyte Ransomware Targets Windows Users with Advanced Encryption Techniques

A new ransomware variant, known as Ebyte Ransomware, has emerged as a significant threat...

macOS NULL Pointer Dereference Vulnerability Allow Attackers Exploits Kernel

Historically, NULL pointer dereferences have been a significant vulnerability in operating systems, including macOS....

Apache Camel Vulnerability Allows Attackers to Inject Arbitrary Headers

A newly disclosed security vulnerability in Apache Camel, tracked as CVE-2025-27636, has raised alarms across...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Threat Actors Evade Security Measures to Launch SIM Swap Attacks

SIM swapping fraud continues to pose a significant threat to individuals and financial institutions,...

Ebyte Ransomware Targets Windows Users with Advanced Encryption Techniques

A new ransomware variant, known as Ebyte Ransomware, has emerged as a significant threat...

macOS NULL Pointer Dereference Vulnerability Allow Attackers Exploits Kernel

Historically, NULL pointer dereferences have been a significant vulnerability in operating systems, including macOS....