VulnerableCode Package Details - pkg:apache/tomcat@7.0.99

Search for packages

Vulnerability	Summary	Fixed by
VCID-eb37-mkxf-7fgw 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.	7.0.100 Affected by 0 other vulnerabilities. 8.5.51 Affected by 0 other vulnerabilities. 9.0.31 Affected by 0 other vulnerabilities.
VCID-rq42-qvsy-hue6 Aliases: CVE-2019-17569 GHSA-767j-jfh2-jvrc	The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading 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.	7.0.100 Affected by 0 other vulnerabilities. 8.5.51 Affected by 0 other vulnerabilities. 9.0.31 Affected by 0 other vulnerabilities.
VCID-yfx4-4gsc-2kgh 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.	7.0.100 Affected by 0 other vulnerabilities. 8.5.51 Affected by 0 other vulnerabilities. 9.0.31 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-eb37-mkxf-7fgw
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.

7.0.100
Affected by 0 other vulnerabilities.

8.5.51
Affected by 0 other vulnerabilities.

9.0.31
Affected by 0 other vulnerabilities.

VCID-rq42-qvsy-hue6
Aliases:
CVE-2019-17569
GHSA-767j-jfh2-jvrc

The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading 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.

7.0.100
Affected by 0 other vulnerabilities.

8.5.51
Affected by 0 other vulnerabilities.

9.0.31
Affected by 0 other vulnerabilities.

VCID-yfx4-4gsc-2kgh
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.

7.0.100
Affected by 0 other vulnerabilities.

8.5.51
Affected by 0 other vulnerabilities.

9.0.31
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
VCID-dzpn-w4b3-vbcm	When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.	CVE-2019-17563 GHSA-9xcj-c8cr-8c3c
VCID-ruuh-g3fa-m7d8	When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.	CVE-2019-12418 GHSA-hh3j-x4mc-g48r

Vulnerability

Summary

Aliases

VCID-dzpn-w4b3-vbcm

When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.

CVE-2019-17563
GHSA-9xcj-c8cr-8c3c

VCID-ruuh-g3fa-m7d8

When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

CVE-2019-12418
GHSA-hh3j-x4mc-g48r

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-01T12:38:13.704181+00:00	Apache Tomcat Importer	Fixing	VCID-ruuh-g3fa-m7d8	https://tomcat.apache.org/security-7.html	38.0.0
2026-04-01T12:38:13.675054+00:00	Apache Tomcat Importer	Fixing	VCID-dzpn-w4b3-vbcm	https://tomcat.apache.org/security-7.html	38.0.0
2026-04-01T12:38:13.646928+00:00	Apache Tomcat Importer	Affected by	VCID-rq42-qvsy-hue6	https://tomcat.apache.org/security-7.html	38.0.0
2026-04-01T12:38:13.621081+00:00	Apache Tomcat Importer	Affected by	VCID-yfx4-4gsc-2kgh	https://tomcat.apache.org/security-7.html	38.0.0
2026-04-01T12:38:13.590081+00:00	Apache Tomcat Importer	Affected by	VCID-eb37-mkxf-7fgw	https://tomcat.apache.org/security-7.html	38.0.0