Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2020-1938

KEV EPSS 94.47% · P100
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2020-1938

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability 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: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Apache Tomcat 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Apache Tomcat是美国阿帕奇(Apache)基金会的一款轻量级Web应用服务器。该程序实现了对Servlet和JavaServer Page(JSP)的支持。 Apache Tomcat 7.0.100版本之前的7.*版本、8.5.51版本之前的8.*版本和9.0.31版本之前的9.*版本中的Tomcat AJP协议存在安全漏洞。攻击者可利用该漏洞读取或包含Tomcat上所有webapp目录下的任意文件,如 webapp 配置文件或源代码等。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Shenlong Deep Dive — AI Deep Analysis

10-question deep dive: root cause, exploitation, mitigation, urgency. Read summary free, full version requires login.

Affected Products

VendorProductAffected VersionsCPESubscribe
ApacheApache Tomcat Apache Tomcat 9.0.0.M1 to 9.0.0.30 -

II. Public POCs for CVE-2020-1938

#POC DescriptionSource LinkShenlong Link
1Nonehttps://github.com/xindongzhuaizhuai/CVE-2020-1938POC Details
2CVE-2020-1938https://github.com/sgdream/CVE-2020-1938POC Details
3CNVD-2020-10487(CVE-2020-1938), tomcat ajp 文件读取漏洞pochttps://github.com/nibiwodong/CNVD-2020-10487-Tomcat-ajp-POCPOC Details
4Cnvd-2020-10487 / cve-2020-1938, scanner toolhttps://github.com/bkfish/CNVD-2020-10487-Tomcat-Ajp-lfi-ScannerPOC Details
5CVE-2020-1938漏洞复现https://github.com/laolisafe/CVE-2020-1938POC Details
6Nonehttps://github.com/h7hac9/CVE-2020-1938POC Details
7Tomcat的文件包含及文件读取漏洞利用POChttps://github.com/sv3nbeast/CVE-2020-1938-Tomact-file_include-file_readPOC Details
8在一定条件下可执行命令https://github.com/fairyming/CVE-2020-1938POC Details
9Nonehttps://github.com/dacade/CVE-2020-1938POC Details
10批量扫描TomcatAJP漏洞https://github.com/woaiqiukui/CVE-2020-1938TomcatAjpScannerPOC Details
11Nonehttps://github.com/fatal0/tomcat-cve-2020-1938-checkPOC Details
12CVE-2020-1938https://github.com/ze0r/GhostCat-LFI-expPOC Details
13CNVD-2020-10487 OR CVE-2020-1938 批量验证脚本,批量验证,并自动截图,方便提交及复核https://github.com/delsadan/CNVD-2020-10487-Bulk-verificationPOC Details
14Ghostcat read file/code execute,CNVD-2020-10487(CVE-2020-1938) https://github.com/00theway/Ghostcat-CNVD-2020-10487POC Details
15Learnings on how to verify if vulnerable to Ghostcat (aka CVE-2020-1938)https://github.com/shaunmclernon/ghostcat-verificationPOC Details
16Test Explo for Ghostcat CVE-2020-1938https://github.com/Zaziki1337/Ghostcat-CVE-2020-1938POC Details
17CVE-2020-1938(GhostCat) clean and readable code versionhttps://github.com/w4fz5uck5/CVE-2020-1938-Clean-VersionPOC Details
18批量检测幽灵猫漏洞https://github.com/Just1ceP4rtn3r/CVE-2020-1938-ToolPOC Details
19CVE-2020-1938 / CNVD-2020-1048 Detection Toolshttps://github.com/doggycheng/CNVD-2020-10487POC Details
20This is about CVE-2020-1938https://github.com/I-Runtime-Error/CVE-2020-1938POC Details
21CVE-2020-1938 exploithttps://github.com/Umesh2807/GhostcatPOC Details
22Disables AJP connectors to remediate CVE-2020-1938!https://github.com/MateoSec/ghostcatchPOC Details
23Modified version of auxiliary/admin/http/tomcat_ghostcat, it can Read any filehttps://github.com/acodervic/CVE-2020-1938-MSF-MODULEPOC Details
24Nonehttps://github.com/Hancheng-Lei/Hacking-Vulnerability-CVE-2020-1938-GhostcatPOC Details
25Nonehttps://github.com/streghstreek/CVE-2020-1938POC Details
26Scanner for CVE-2020-1938https://github.com/Neko-chanQwQ/CVE-2020-1938POC Details
27An implementation of CVE-2020-1938https://github.com/jptr218/ghostcatPOC Details
28-H 192.168.1.1-192.168.5.255https://github.com/einzbernnn/CVE-2020-1938ScanPOC Details
29This is a modified version of the original GhostCat Exploithttps://github.com/YounesTasra-R4z3rSw0rd/CVE-2020-1938POC Details
30cve-2020-1938 Tomcat-Ajp-lfi.git脚本https://github.com/Warelock/cve-2020-1938POC Details
31CVE-2020-1938https://github.com/whatboxapp/GhostCat-LFI-expPOC Details
32This is exploit of CVE-2020-1938 Ghostcat-Apache Tomcat Vulnerabilityhttps://github.com/technicalcorp2/CVE-2020-1938-ExploitPOC Details
33cve-2020-1938 POC, updated versionhttps://github.com/s3nd3rjz/poc-CVE-2020-1938POC Details
34Nonehttps://github.com/WHtig3r/CVE-2020-1938POC Details
35poc-CVE-2020-1938https://github.com/aib0litt/poc-CVE-2020-1938POC Details
36Nonehttps://github.com/hopsypopsy8/CVE-2020-1938-ExploitationPOC Details
37Apache Tomcat vulnerable to Ghostcat (CVE-2020-1938).https://github.com/erickrr-bd/Apache-Tomcat-Ghostcat-VulnerabilityPOC Details
38When 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.https://github.com/projectdiscovery/nuclei-templates/blob/main/network/cves/2020/CVE-2020-1938.yamlPOC Details
39Nonehttps://github.com/Threekiii/Awesome-POC/blob/master/%E4%B8%AD%E9%97%B4%E4%BB%B6%E6%BC%8F%E6%B4%9E/Apache%20Tomcat%20AJP%20%E6%96%87%E4%BB%B6%E5%8C%85%E5%90%AB%E6%BC%8F%E6%B4%9E%20CVE-2020-1938.mdPOC Details
40https://github.com/vulhub/vulhub/blob/master/tomcat/CVE-2020-1938/README.mdPOC Details
41Ghostcat read file/code execute,CNVD-2020-10487(CVE-2020-1938)https://github.com/Joshua8821/CNVDPOC Details
42Apache Tomcat AJP Ghostcat (CVE-2020-1938) exploit tool for file disclosure with multi-target scanning, custom wordlists, and upload point detection capabilitieshttps://github.com/abrewer251/CVE-2020-1938_Ghostcat-PoCPOC Details
43Nonehttps://github.com/RedTeam-Rediron/CVE-2020-1938POC Details
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-1938

登录查看更多情报信息。

Same Patch Batch · Apache · 2020-02-24 · 4 CVEs total

CVE-2020-1935Apache Tomcat 环境问题漏洞
CVE-2019-17569Apache Tomcat 环境问题漏洞
CVE-2020-1937Apache Kylin SQL注入漏洞

IV. Related Vulnerabilities

V. Comments for CVE-2020-1938

No comments yet


Leave a comment