CVE-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…

Browse: All 2020 CVEs · All vendors

CVSS score
9.8 Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA KEV
Yes — actively exploited (added 2022-03-03, remediation due 2022-03-17)
Weakness (CWE)
NVD-CWE-Other
Published
2020-02-24
Last modified
2026-08-25
NVD status
Analyzed

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.

Affected products

Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.

Required action (CISA)

Apply updates per vendor instructions. Federal remediation deadline: 2022-03-17.

How to prioritize this

This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score. For the actively exploited vulnerabilities that matter this week, read The Exploit HQ daily security brief.

References

FAQ

Is CVE-2020-1938 actively exploited?

Yes. CISA added CVE-2020-1938 to its Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03, with a federal remediation deadline of 2022-03-17. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.

What is the CVSS score of CVE-2020-1938?

CVE-2020-1938 has a CVSS base score of 9.8 (Critical). Its vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Related vulnerabilities

Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.