Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2020-1938

tomcat: Apache Tomcat AJP File Read/Inclusion Vulnerability

Overview

Published
24 Feb 2020
Modified
25 Aug 2026
Critical CVE
4 Registry packages
197 OS packages
7 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages · 4

Packages affected by CVE-2020-1938
EcosystemPackageVulnerableFixed in
Bitnami tomcat >=7.0.0, <7.0.100>=8.5.0, <8.5.51>=9.0.0, <9.0.31 7.0.1008.5.519.0.31
Maven org.apache.tomcat.embed:tomcat-embed-core >=9.0.0, <9.0.31>=8.0.0, <8.5.51>=7.0.0, <7.0.100 9.0.318.5.517.0.100
Seal Maven org.apache.tomcat.embed:tomcat-embed-core >=8.5.46+sp0, <8.5.46+sp999 8.5.46+sp999
Seal Maven seal.sp1.org.apache.tomcat.embed:tomcat-embed-core >=8.5.46, <8.5.46+sp999 8.5.46+sp999

Open a package to see all its vulnerabilities.

Operating systems · 94 fixes

Oracle Linux 1 release · 1 package

fixed 1
tomcat
Oracle Linux fixes for CVE-2020-1938
ReleasePackageFixed in
7 tomcat +9 7.0.76-11.el7_7

Red Hat 5 releases · 47 packages

affected 2 wont fix 1 fixed 49
opendaylight ironjacamar-common-api-eap6 weld-core jboss-remoting3-jmx glassfish-jsf12-eap6 tomcat-native +41
Red Hat fixes for CVE-2020-1938
ReleasePackageFixed inAdvisory
7 opendaylight affected —
7 opendaylight wont fix —
7 ironjacamar-common-api-eap6 +9 0:1.0.44-1.Final_redhat_00001.1.ep6.el7 RHSA-2020:2780
7 weld-core 0:1.1.34-2.Final_redhat_2.1.ep6.el7 RHSA-2020:2780
7 jboss-remoting3-jmx 0:1.1.4-2.Final_redhat_00001.1.ep6.el7 RHSA-2020:2780
7 glassfish-jsf12-eap6 0:1.2.15-11.b01_SP2_redhat_2.1.ep6.el7 RHSA-2020:2780

46 more rows

SUSE Linux Enterprise 1 release · 2 packages

fixed 2
apache2 tomcat
SUSE Linux Enterprise fixes for CVE-2020-1938
ReleasePackageFixed inAdvisory
12.5 apache2 +6 2.4.23-29.54.1 SUSE-SU-2020:1272-1
12.5 tomcat +8 9.0.31-3.25.1 SUSE-SU-2020:0632-1

debian 6 releases · 3 packages

fixed 6 affected 1
tomcat9 tomcat7 tomcat8
debian fixes for CVE-2020-1938
ReleasePackageFixed in
10 tomcat9 9.0.31-1~deb10u1
11 tomcat9 9.0.31-1
12 tomcat9 9.0.31-1
13 tomcat9 9.0.31-1
14 tomcat9 9.0.31-1
9 tomcat7 affected

1 more row

echo 1 release · 1 package

fixed 1
tomcat9
echo fixes for CVE-2020-1938
ReleasePackageFixed in
tomcat9 9.0.31-1

openSUSE 1 release · 2 packages

fixed 2
tomcat10 tomcat
openSUSE fixes for CVE-2020-1938
ReleasePackageFixed inAdvisory
Tumbleweed tomcat10 +10 10.1.14-1.1 openSUSE-SU-2024:13441-1
Tumbleweed tomcat +10 9.0.36-8.4 openSUSE-SU-2024:11468-1

rocky 3 releases · 27 packages

fixed 29
slf4j ldapjdk xsom python-nss-doc xml-commons-resolver bea-stax-api +21
rocky fixes for CVE-2020-1938
ReleasePackageFixed in
8 (maven:3.5) slf4j 1.7.25-4.module+el8.3.0+133+b8b54b58
8 (pki-core:10.6) ldapjdk +1 4.22.0-1.module+el8.4.0+418+b7ae1d4a
8 (pki-deps:10.6) xsom 0-19.20110809svn.module+el8.3.0+53+ea062990
8 (pki-deps:10.6) python-nss-doc +1 1.0.1-10.module+el8.3.0+53+ea062990
8 (pki-deps:10.6) xml-commons-resolver 1.2-26.module+el8.3.0+53+ea062990
8 (pki-deps:10.6) bea-stax-api 1.2.0-16.module+el8.3.0+53+ea062990

23 more rows

References

Show all 165 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.