Outdated Apache Tomcat

An application server runs an Apache Tomcat release that is missing security fixes or a major version that has reached end of life.

SeverityHigh
CVSS 3.18.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services
CategoryOutdated Components

Description

An application server runs a release of Apache Tomcat that predates fixes for one or more published vulnerabilities, or a major version that has reached end of life. The Tomcat project publishes a list of fixed vulnerabilities for each supported major version, linking each fix to its source change but never providing binary patches, so fixes are obtained by upgrading.

Past Tomcat issues show what an attacker may be able to do, depending on the vulnerabilities and the configuration: read application files and configuration, including credentials, through the file read and inclusion flaw in the AJP connector (CVE-2020-1938, known as Ghostcat); run code on the server through JSP files (CVE-2017-12617) or session files (CVE-2025-24813) uploaded when the default servlet allowed writes; smuggle requests past front-end controls; or exploit session fixation, information disclosure and denial of service. Many depend on a non-default configuration, such as an exposed AJP port, writes enabled on the default servlet or file-based session persistence. Several, including Ghostcat and CVE-2025-24813, are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue. Code execution runs with the privileges of the account that runs Tomcat, which in poorly hardened installations is root or SYSTEM, and the risk is greatest where Tomcat is internet-facing or its AJP connector or management applications are reachable from untrusted networks.

The finding is usually raised from the version shown on default error pages, the default home page and the documentation and manager applications, or from an authenticated scan of the installation's files, and scanners report one result per advisory affecting that version, seldom checking the configuration it depends on. Tomcat packaged by Linux distributions may carry backported fixes without a version change, and Tomcat embedded in other products or in applications, such as Spring Boot applications, is updated through those products and their dependency management.

Remediation

Upgrade Tomcat and remove risky configuration:

  • Upgrade to the latest release of a currently supported Tomcat major version, as listed by the Apache Tomcat project, migrating applications off any major version that has reached end of life. Where Tomcat comes from a distribution package, install its latest update; where it is embedded in an application, update the Tomcat dependency and rebuild.
  • Disable the AJP connector if it is not needed, or bind it to the loopback interface and set a secret on it, and never expose it to untrusted networks.
  • Keep the default servlet read-only, with its readonly parameter at the default of true, and remove the example, documentation, manager and host-manager applications from production or restrict them to administrators' networks.
  • Run Tomcat under a dedicated low-privileged account.

Confirm the fix by checking the version with the version.sh or version.bat script in the installation's bin directory, reviewing the configuration changes above, and repeating the scan.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding