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...
Basic Information
- CVE State
- PUBLISHED
- Reserved Date
- December 02, 2019
- Published Date
- February 24, 2020
- Last Updated
- February 06, 2025
- Vendor
- Apache Software Foundation
- Product
- Apache Tomcat
- 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.
- Tags
- Exploitation
- active
- Automatable
- Yes
- Technical Impact
- total
CVSS Scores
CVSS v3.1
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v2.0
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P
SSVC Information
References
Known Exploited Vulnerability Information
| Source | Added Date |
|---|---|
| CISA | 2022-03-03 00:00:00 UTC |
Scanner Integrations
| Scanner | URL | Date Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/network/cves/2020/CVE-2020-1938.yaml | 2025-04-26 00:00:00 UTC |
Potential Proof of Concepts
Warning: These PoCs have not been tested and could contain malware. Use at your own risk.
YounesTasra-R4z3rSw0rd/CVE-2020-1938
Type: github • Created: 2022-08-21 15:44:45 UTC • Stars: 3
Neko-chanQwQ/CVE-2020-1938
Type: github • Created: 2021-07-11 14:38:21 UTC • Stars: 1
streghstreek/CVE-2020-1938
Type: github • Created: 2021-04-27 14:57:30 UTC • Stars: 1
Hancheng-Lei/Hacking-Vulnerability-CVE-2020-1938-Ghostcat
Type: github • Created: 2021-03-28 03:30:44 UTC • Stars: 15
I-Runtime-Error/CVE-2020-1938
Type: github • Created: 2020-05-12 15:54:28 UTC • Stars: 0
Just1ceP4rtn3r/CVE-2020-1938-Tool
Type: github • Created: 2020-03-20 09:29:18 UTC • Stars: 3
w4fz5uck5/CVE-2020-1938-Clean-Version
Type: github • Created: 2020-03-01 01:45:23 UTC • Stars: 6
woaiqiukui/CVE-2020-1938TomcatAjpScanner
Type: github • Created: 2020-02-21 14:55:40 UTC • Stars: 15
dacade/CVE-2020-1938
Type: github • Created: 2020-02-21 09:56:19 UTC • Stars: 9
fairyming/CVE-2020-1938
Type: github • Created: 2020-02-21 08:42:50 UTC • Stars: 11
sv3nbeast/CVE-2020-1938-Tomact-file_include-file_read
Type: github • Created: 2020-02-21 07:48:50 UTC • Stars: 53
laolisafe/CVE-2020-1938
Type: github • Created: 2020-02-21 02:36:37 UTC • Stars: 37
xindongzhuaizhuai/CVE-2020-1938
Type: github • Created: 2020-02-20 17:00:02 UTC • Stars: 45
Timeline
-
CVE ID Reserved
-
CVE Published to Public
-
Proof of Concept Exploit Available
-
Added to KEVIntel
-
Detected by Nuclei