forked from CheckmarxDev/JavaVulnerableLab
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CX: CVE-2020-1938 in Maven-org.apache.tomcat:tomcat-coyote and 9.0.22 @ RM_JavaVulnerableLab.refs/heads/master #13
Comments
Issue still exists. |
Issue still exists. |
Issue still exists. |
Issue still exists. |
Issue still exists. |
1 similar comment
Issue still exists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
HIGH Vulnerable Package issue exists @ org.apache.tomcat:tomcat-coyote in branch refs/heads/master
Vulnerability ID: CVE-2020-1938
Package Name: org.apache.tomcat:tomcat-coyote
Severity: HIGH
CVSS Score: 9.8
Publish Date: 2020-02-24T22:15:00
Current Package Version: 9.0.22
Remediation Upgrade Recommendation: 9.0.48
Link To SCA
Reference – NVD link
The text was updated successfully, but these errors were encountered: