Search for packages
| purl | pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.25 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1fkk-yntx-hyfd
Aliases: CVE-2020-1938 GHSA-c9hw-wf7x-jp9j |
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. |
Affected by 2 other vulnerabilities. Affected by 12 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-7fh6-ur9z-uqcw
Aliases: CVE-2013-2185 GHSA-v6c7-8qx5-8gmp |
Affected by 7 other vulnerabilities. Affected by 7 other vulnerabilities. |
|
|
VCID-97sa-54jq-a3fc
Aliases: CVE-2014-0075 GHSA-475f-74wp-pqv5 |
Affected by 5 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 1 other vulnerability. |
|
|
VCID-gb8p-hr5j-yqav
Aliases: CVE-2014-0050 GHSA-xx68-jfcg-xmmf |
Affected by 6 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
|
VCID-j52h-jxrq-43g1
Aliases: CVE-2016-6816 GHSA-jc7p-5r39-9477 |
Affected by 4 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 14 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 1 other vulnerability. |
|
|
VCID-s87f-pf8e-yqcz
Aliases: CVE-2021-24122 GHSA-2rvv-w9r2-rg7m |
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances. |
Affected by 0 other vulnerabilities. Affected by 6 other vulnerabilities. Affected by 7 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-x36b-25k2-ckcx
Aliases: CVE-2020-1935 GHSA-qxf4-chvg-4r8r |
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely. |
Affected by 2 other vulnerabilities. Affected by 12 other vulnerabilities. Affected by 13 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||