Skip to content
Server Security Center
KEVcritical9.8

CVE-2020-1938: Apache Tomcat Improper Privilege Management

Apache Tomcat · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
99.2%
among the highest 0.1% of all CVEs
Added to CISA KEV
2022-03-03
US federal due date 2022-03-17
Ubuntu priority
low

CVE-2020-1938 explained

CVE-2020-1938 is a flaw in how Apache Tomcat trusts connections on its AJP Connector. Affected Tomcat versions shipped with the AJP Connector enabled by default on all configured IP addresses. If that port is reachable by an attacker, Tomcat can be made to return arbitrary files from the web application or process files as JSP. It is listed in the CISA Known Exploited Vulnerabilities catalog.

Impact

An unauthenticated attacker with network access to an AJP port can read arbitrary files from anywhere in the web application and have any file in the web application processed as a JSP. If the application allows file uploads stored inside the web application, or the attacker can otherwise control its content, remote code execution is possible. Mitigation is only required when an AJP port is accessible to untrusted users.

Who is affected

Ubuntu lists no fixed version for any affected package. Ubuntu 14.04 LTS (tomcat7) and Ubuntu 16.04 LTS (tomcat7, tomcat8) are end of life. Ubuntu 18.04 LTS (tomcat7, tomcat8, tomcat9) has ended standard support, and fixes there would come only through Ubuntu Pro (ESM). Upstream, Tomcat 9.0.31, 8.5.51 and 7.0.100 or later block the file-return and JSP execution vector.

Written with AI from the data on this page and checked against it automatically.

Official description

When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising.

In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required.

This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users.

Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration.

It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Apache Tomcat
    Affected
    • Apache Tomcat 9.0.0.M1 to 9.0.0.30
    • 8.5.0 to 8.5.50
    • 7.0.0 to 7.0.99
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Check whether any Tomcat AJP Connector is enabled and which addresses it listens on.
  2. Disable the AJP Connector if it is not required.
  3. If AJP is needed, bind it to trusted interfaces only and block the AJP port from untrusted networks with a firewall.
  4. Upgrade systems on Ubuntu 14.04 LTS and 16.04 LTS to a supported release.
  5. On Ubuntu 18.04 LTS, enable Ubuntu Pro (ESM) and apply Tomcat updates when a fix is published, then restart Tomcat.

No fixed package is published for any listed release. Disable the AJP Connector if unused, or restrict it to trusted hosts and block the port from untrusted networks. Review whether web applications store uploaded files inside the application. Upgrade end-of-life Ubuntu 14.04 LTS and 16.04 LTS systems to a supported release. Note that upstream hardening may require small configuration changes.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace tomcat7 with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="tomcat7"'

No fixed version available

No Ubuntu or Debian release has published a fixed version of the affected packages yet, so every installed version is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: lists.apache.org/thread.html/r7c6f492fbd39af34a68681dbbba…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS, Ubuntu 14.04 LTS have reached end of life and no longer get regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Questions about CVE-2020-1938

Am I affected if AJP is not reachable from untrusted networks?
According to the description, mitigation is only required if an AJP port is accessible to untrusted users. Confirm the connector is disabled or limited to trusted hosts.
Why does the Ubuntu priority differ from the critical CVSS rating?
Ubuntu rates this CVE low priority, while the CVE record scores it critical. Exposure depends on whether an AJP port is reachable by untrusted users, so assess your own configuration.
Is this vulnerability exploited in practice?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03. Known ransomware use is listed as unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.