According to its self-reported version number, the Apache Tomcat service running on the remote host is 8.5.x prior to 8.5.13. It is therefore affected by multiple vulnerabilities :

 - A flaw exists in the handling of pipelined requests when send file processing is used that results in the pipelined request being lost when processing of the previous request has completed, causing responses to be sent for the wrong request. An unauthenticated, remote attacker can exploit this to disclose sensitive information. (CVE-2017-5647)

 - A flaw exists in the handling of HTTP/2 GOAWAY frames for a connection due to streams associated with the connection not being properly closed if the connection was currently waiting for a WINDOW_UPDATE before allowing the application to write more data. Each stream consumes a processing thread in the system. An unauthenticated, remote attacker can exploit this issue, via a series of specially crafted HTTP/2 requests, to consume all available threads, resulting in a denial of service condition. (CVE-2017-5650)

 - A flaw exists in HTTP connectors when processing send files. If processing completed quickly, it was possible to add the processor to the processor cache twice, which allows the same processor to be used for multiple requests. An unauthenticated, remote attacker can exploit this to disclose sensitive information from other sessions or cause unexpected errors. (CVE-2017-5651)

Note that the scanner has not attempted to exploit these issues but has instead relied only on the application's self-reported version number.

This updates includes a rebase from tomcat 8.0.42 up to 8.0.43 which resolves multiple CVEs :

  - rhbz#1441242 CVE-2017-5647 CVE-2017-5648 CVE-2017-5650     CVE-2017-5651 tomcat: various flaws

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of Tomcat installed on the remote host is prior to 9.0.0.M19. It is, therefore, affected by multiple vulnerabilities as referenced in the fixed_in_apache_tomcat_9.0.0.m19_security-9 advisory.

  - In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors     introduced a regression in the send file processing. If the send file processing completed quickly, it was     possible for the Processor to be added to the processor cache twice. This could result in the same     Processor being used for multiple requests which in turn could lead to unexpected errors and/or response     mix-up. (CVE-2017-5651)

  - In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a     connection did not close streams associated with that connection that were currently waiting for a     WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a     thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all     available processing threads. (CVE-2017-5650)

  - A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12,     8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the     pipelined request being lost when send file processing of the previous request completed. This could     result in responses appearing to be sent for the wrong request. For example, a user agent that sent     requests A, B and C could see the correct response for request A, the response for request C for request B     and no response for request C. (CVE-2017-5647)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-201705-09 (Apache Tomcat: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Tomcat. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker may be able to cause a Denial of Service condition,       obtain sensitive information, bypass protection mechanisms and       authentication restrictions.
    A local attacker, who is a tomcat&rsquo;s system user or belongs to       tomcat&rsquo;s group, could potentially escalate privileges.
  Workaround :

    There is no known workaround at this time.

The version of Tomcat installed on the remote host is prior to 8.5.13. It is, therefore, affected by multiple vulnerabilities as referenced in the fixed_in_apache_tomcat_8.5.13_security-8 advisory.

  - In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors     introduced a regression in the send file processing. If the send file processing completed quickly, it was     possible for the Processor to be added to the processor cache twice. This could result in the same     Processor being used for multiple requests which in turn could lead to unexpected errors and/or response     mix-up. (CVE-2017-5651)

  - In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a     connection did not close streams associated with that connection that were currently waiting for a     WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a     thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all     available processing threads. (CVE-2017-5650)

  - A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12,     8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the     pipelined request being lost when send file processing of the previous request completed. This could     result in responses appearing to be sent for the wrong request. For example, a user agent that sent     requests A, B and C could see the correct response for request A, the response for request C for request B     and no response for request C. (CVE-2017-5647)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
112304	Apache Tomcat 8.5.x < 8.5.13 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	11/5/2018	3/14/2023	critical
99718	Fedora 25 : 1:tomcat (2017-5261ba4605)	Nessus	Fedora Local Security Checks	4/28/2017	1/6/2021	critical
197828	Apache Tomcat 9.0.0.M1 < 9.0.0.M19 multiple vulnerabilities	Nessus	Web Servers	5/23/2024	5/23/2024	critical
100262	GLSA-201705-09 : Apache Tomcat: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	5/18/2017	1/11/2021	critical
99720	Fedora 24 : 1:tomcat (2017-d5aa7c77d6)	Nessus	Fedora Local Security Checks	4/28/2017	1/6/2021	critical
99368	Apache Tomcat 8.5.0 < 8.5.13 multiple vulnerabilities	Nessus	Web Servers	4/14/2017	5/23/2024	critical
101573	Fedora 26 : 1:tomcat (2017-0e64c4c186)	Nessus	Fedora Local Security Checks	7/17/2017	1/11/2021	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical