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.
This indicates an attack attempt to exploit a Local File Inclusion vulnerability in Apache Tomcat.The vulnerability is due to an error when the vulnerable software handles a maliciously crafted request. A remote attacker may be able to exploit this to gain access to sensitive information.
Apache Tomcat 6
Apache Tomcat 7x Apache Tomcat 8x Apache Tomcat 9x
Information Disclosure: Remote attackers can gain sensitive information from vulnerable systems
Currently we are unaware of any vendor supplied patch for this issue.
CVE Infomation | Exploits or more Infomation |
---|---|
mitre | EXPLOIT DATABASE |
NVD | 0day.today |
vulmon.com | github |
CVE Details | |
JVN ENG JPN | |
Reconshell |
Software Tag: Tomcat(2 tweets)
List of frequently cited URLs
User | URL | Info Source | Date |
---|---|---|---|
thephoenix2023 | https://github.com/Hancheng-Lei/Hacking-Vulnerability-CVE-2... | Source thephoenix2023 1631363229526941700 | 2023/03/03 |
MuzamilGg | https://tryhackme.com/room/tomghost | Source MuzamilGg 1634581004084977670 | 2023/03/12 |
MrMidnight53 | https://tryhackme.com/room/tomghost | Source MrMidnight53 1646817944016437249 | 2023/04/14 |
List of frequently cited URLs
URL | Num of Times Referred to |
---|---|
vulmon.com | 2861 |
lists.astaro.com | 48 |
medium.com | 38 |
twitter.com | 8 |
blog.trendmicro.co.jp | 6 |
www.snort.org | 4 |
fortiguard.com | 4 |
www.checkpoint.com | 4 |
www.proofpoint.com | 4 |
www.watchguard.com | 4 |
update1.hillstonenet.com | 4 |
go.shr.lc | 3 |
github.com | 3 |
tryhackme.com | 3 |
User | URL | Info Source |
---|---|---|
thephoenix2023 | github.com | Show Tweet |
MuzamilGg | tryhackme.com | Show Tweet |
MrMidnight53 | tryhackme.com | Show Tweet |
Name | URL |
---|---|
No Data |
Name | URL |
---|---|
No Data |