Homepage
About Snyk

CVE-2020-1938 Affecting tomcat-el-3_0-api package, versions <9.0.31-3.42.2

0.0
high

Snyk CVSS

    Exploit Maturity Mature
    Attack Complexity Low
    User Interaction Required
    Confidentiality High
    Integrity High
Expand this section
NVD
9.8 critical
Expand this section
SUSE
7.6 high
Expand this section
Red Hat
7.6 high

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-SLES150-TOMCATEL30API-2714266
  • published 14 Apr 2022
  • disclosed 5 Mar 2020
Report a new vulnerability Found a mistake?

Introduced: 5 Mar 2020

CVE-2020-1938 Open this link in a new tab

How to fix?

Upgrade SLES:15.0 tomcat-el-3_0-api to version 9.0.31-3.42.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-el-3_0-api package and not the tomcat-el-3_0-api package as distributed by SLES:15.0. See How to fix? for SLES:15.0 relevant fixed versions and status.

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.

References