VulnerableCode Package Details - pkg:rpm/redhat/tomcat8@8.0.36-42.ep7?arch=el6

Search for packages

Vulnerability	Summary	Fixed by
VCID-arkn-bca7-hqam Aliases: CVE-2019-0221 GHSA-jjpq-gp5q-8q6w	The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.	There are no reported fixed by versions.
VCID-dzpn-w4b3-vbcm Aliases: CVE-2019-17563 GHSA-9xcj-c8cr-8c3c	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.	There are no reported fixed by versions.
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.	There are no reported fixed by versions.
VCID-ruuh-g3fa-m7d8 Aliases: CVE-2019-12418 GHSA-hh3j-x4mc-g48r	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.	There are no reported fixed by versions.

Vulnerability

Summary

Fixed by

VCID-arkn-bca7-hqam
Aliases:
CVE-2019-0221
GHSA-jjpq-gp5q-8q6w

The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.

There are no reported fixed by versions.

VCID-dzpn-w4b3-vbcm
Aliases:
CVE-2019-17563
GHSA-9xcj-c8cr-8c3c

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.

There are no reported fixed by versions.

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.

There are no reported fixed by versions.

VCID-ruuh-g3fa-m7d8
Aliases:
CVE-2019-12418
GHSA-hh3j-x4mc-g48r

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.

There are no reported fixed by versions.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-01T14:20:09.897746+00:00	RedHat Importer	Affected by	VCID-arkn-bca7-hqam	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2019-0221.json	38.0.0
2026-04-01T14:15:02.354433+00:00	RedHat Importer	Affected by	VCID-ruuh-g3fa-m7d8	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2019-12418.json	38.0.0
2026-04-01T14:14:34.820360+00:00	RedHat Importer	Affected by	VCID-dzpn-w4b3-vbcm	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2019-17563.json	38.0.0
2026-04-01T14:12:26.497726+00:00	RedHat Importer	Affected by	VCID-eb37-mkxf-7fgw	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2020-1938.json	38.0.0