ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2020-1938

Apache Tomcat Improper Privilege Management Vulnerability

Published Feb 24, 2020 · catalog updated Aug 25, 2026 · Apache Tomcat

Patch now

CVE-2020-1938 is in the CISA known-exploited catalog, due Mar 17, 2022. Confirm Apache Tomcat against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Severity
Critical9.8
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
99.27%
Remediation
Remediation guidance
Affected products
cpe apache/geode · cpe apache/tomcat · cpe blackberry/good control · cpe debian/debian linux · cpe fedoraproject/fedora · cpe netapp/data availability services

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/geode1.12.0
  • cpe apache/tomcatversion unspecified
  • cpe blackberry/good controlversion unspecified
  • cpe debian/debian linux8.0
  • cpe fedoraproject/fedora30
  • cpe fedoraproject/fedora31
  • cpe fedoraproject/fedora32
  • cpe netapp/data availability servicesversion unspecified
  • cpe opensuse/leap15.1
  • cpe oracle/agile engineering data management6.2.1.0
  • vendor Apache Tomcatversion unspecified

How to fix CVE-2020-1938

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2020-1938 is in the CISA known-exploited catalog, due Mar 17, 2022. Confirm Apache Tomcat against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Compare what you have installed with debian/debian linux 8.0; oracle/agile engineering data management 6.2.1.0. Apply updates per vendor instructions.

What should an analyst verify?

No weakness class is stored. EPSS 99.27%. The CISA KEV listing is the exploitation evidence. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 24, 2020 · Catalog

    Detected

    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, Tomca

  2. Mar 3, 2022 · CISA KEV

    Known exploited

    Apply updates per vendor instructions.

  3. Mar 17, 2022 · CISA KEV

    Remediation due

    Apply updates per vendor instructions.

  4. Aug 25, 2026 · Catalog

    Updated

    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, Tomca

Sources

  • CISA KEVConfirmed exploitationCVE-2020-1938

    Apache Tomcat treats Apache JServ Protocol (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.

    cisa.gov
  • CVE.orgVulnerability recordCVE-2020-1938

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2020-1938

    30-day exploitation probability 99.3%

    first.org
  • Exploit DatabasePublic exploit reference48143

    Public archive entry. The exploit body is not stored here.

    exploit-db.com
  • Exploit DatabasePublic exploit reference49039

    Public archive entry. The exploit body is not stored here.

    exploit-db.com
  • Metasploit ModulesPublic exploit moduleauxiliary_admin/http/tomcat_ghostcat

    Public module reference (normal). Module source is not copied into this catalog.

    rapid7.com
  • NIST NVDVulnerability recordCVE-2020-1938

    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 exp

    nvd.nist.gov
  • VulnCheck KEVConfirmed exploitationCVE-2020-1938

    Apache Tomcat treats Apache JServ Protocol (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.

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.