CISA list

● Branch of Apache Tomcat

Apache Tomcat 8.0

Apache Tomcat 8.0 reached end of life on 30 June 2018 and gets no fixes. Move to 9.0.124 or newer.

Data: .

Records with no fixed release for 8.0

These records name the branch as affected and name no release that ends the range.

Records with no fixed release for 8.0
RecordSigns of exploitationFixed in
CVE-2017-12617Remote Code Execution8.1 High · published 3 October 2017On CISA's list
Metasploit module
Exploit-DB entry
EPSS 0.50 or more
The record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2018-8034The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to…7.5 High · published 1 August 2018NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2018-8014The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all…published 16 May 2018NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2018-1336An improper handing of overflow in the UTF-8 decoder with supplementary characters can lead to an infinite loop in the decoder causing a Denial of Service. Versions Affected: Apache Tomcat 9.0.0.M9…published 2 August 2018NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2017-5664The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are…published 6 June 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2017-5647A 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…published 17 April 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2016-8745A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48…published 10 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2017-5648While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use…published 17 April 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2016-5018In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a…published 10 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2017-7674The CORS Filter in Apache Tomcat 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15, 8.0.0.RC1 to 8.0.44 and 7.0.41 to 7.0.78 did not add an HTTP Vary header indicating that the response varies depending on…published 11 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.
CVE-2016-6797The ResourceLinkFactory implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not limit web application access to global…published 10 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2016-6796A malicious web application running on Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager…published 11 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2016-0762The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the…published 10 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2016-6794When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4…published 10 August 2017NoneThe record names no fixed release for 9.0, 8.5, 8.0, 7 and 6.
CVE-2017-15706As part of the fix for bug 61201, the documentation for Apache Tomcat 9.0.0.M22 to 9.0.1, 8.5.16 to 8.5.23, 8.0.45 to 8.0.47 and 7.0.79 to 7.0.82 included an updated description of the search…published 31 January 2018NoneThe record names no fixed release for 9.0, 8.5, 8.0 and 7.

Apache Tomcat 8.0 in dates

WhatWhen
Released29 January 2014
Security fixes end30 June 2018
Newest release8.0.53 (29 June 2018)

More Apache Tomcat pages

What this page says

This page reads 140 CVE records that the Apache Software Foundation's CVE Numbering Authority has published since 30 June 2018 and that name Apache Tomcat. 28 of them are not placed on a branch. Of the others, 2 name Apache Tomcat 8.0.

No release of Apache Tomcat 8.0 is called safe here, because the branch has ended, whatever the records say of it.

A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)