Sunday, March 23, 2025
HomeCVE/vulnerabilityHackers Actively Exploit Apache Tomcat Servers via CVE-2025-24813 – Patch Now

Hackers Actively Exploit Apache Tomcat Servers via CVE-2025-24813 – Patch Now

Published on

SIEM as a Service

Follow Us on Google News

A concerning development has emerged with the active exploitation of Apache Tomcat servers through the recently disclosed vulnerability, CVE-2025-24813.

This vulnerability allows attackers to potentially execute remote code (RCE) if successfully exploited.

The cybersecurity firm GreyNoise has identified multiple IPs involved in these attacks across several regions, highlighting the urgency for organizations to update their systems immediately.

CVE-2025-24813: A Growing Threat

CVE-2025-24813 is capable of enabling remote code execution, which poses significant risks to the security of systems running Apache Tomcat.

The good news is that the current exploitation seems limited to naive attackers using publicly available proof-of-concept (PoC) code.

However, this could be a precursor to more sophisticated attacks as the vulnerability becomes widely known.

GreyNoise has created a specific CVE-2025-24813 tag to help defenders track and respond to these malicious activities efficiently.

Since March 17, 2025, GreyNoise has detected four unique IPs attempting to exploit this vulnerability.

These attackers are using a partial PUT method to inject malicious payloads, which could lead to arbitrary code execution on vulnerable systems. The geographic distribution of these attempts highlights a diverse range of targets:

  • Geographic Distribution: The majority of exploit attempts have been directed at systems in the United States, Japan, India, South Korea, and Mexico, with over 70% of sessions aimed at U.S.-based systems.
  • Attack Origin: The earliest exploitation attempts were observed on March 11, but significant activity was noted starting from a Latvia-based IP on March 18. Subsequent attempts were traced to Italy, the United States, and China. Notably, two of these IPs are linked to a known VPN service, indicating potential evasion tactics.

Mitigations & Recommendations

Given the seriousness of CVE-2025-24813 and the ongoing exploitation, organizations must take immediate action to secure their systems:

  1. Apply Patches: Organizations should promptly apply the latest security patches for Apache Tomcat.
  2. Monitor Web Server Logs: Regularly monitor for unexpected PUT requests to detect potential attacks.
  3. Deploy WAF Rules: Configure Web Application Firewall (WAF) rules to block malicious payloads effectively.
  4. Use GreyNoise Intelligence: Utilize GreyNoise’s real-time tracking capabilities to identify and block malicious IPs.

Organizations should assess their Apache Tomcat deployments urgently and apply patches to mitigate the risks associated with CVE-2025-24813.

Investigate Real-World Malicious Links & Phishing Attacks With Threat Intelligence Lookup - Try 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

Attackers Leverage Weaponized CAPTCHAs to Execute PowerShell and Deploy Malware

In a recent surge of sophisticated cyberattacks, threat actors have been utilizing fake CAPTCHA...

Researchers Uncover FIN7’s Stealthy Python-Based Anubis Backdoor

Researchers have recently discovered a sophisticated Python-based backdoor, known as the Anubis Backdoor, deployed...

Researchers Reveal macOS Vulnerability Exposing System Passwords

A recent article by Noah Gregory has highlighted a significant vulnerability in macOS, identified...

JumpServer Flaws Allow Attackers to Bypass Authentication and Gain Full Control

JumpServer, a widely used open-source Privileged Access Management (PAM) tool developed by Fit2Cloud, has...

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

Attackers Leverage Weaponized CAPTCHAs to Execute PowerShell and Deploy Malware

In a recent surge of sophisticated cyberattacks, threat actors have been utilizing fake CAPTCHA...

Researchers Uncover FIN7’s Stealthy Python-Based Anubis Backdoor

Researchers have recently discovered a sophisticated Python-based backdoor, known as the Anubis Backdoor, deployed...

Researchers Reveal macOS Vulnerability Exposing System Passwords

A recent article by Noah Gregory has highlighted a significant vulnerability in macOS, identified...