CISA list

● Branch of Apache Tomcat

Apache Tomcat 6

Apache Tomcat 6 reached end of life on 31 December 2016. Move to 9.0.124 or newer.

Data: .

Records with no fixed release for 6

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

Records with no fixed release for 6
RecordSigns of exploitationFixed in
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-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-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.

Apache Tomcat 6 in dates

WhatWhen
Released21 October 2006
End of life31 December 2016
Newest release6.0.53 (2 April 2017)

What this page says

The lifecycle data lists 6.0.53 (2 April 2017) for Apache Tomcat 6, after its end of life on 31 December 2016. This page cannot tell whether that release fixes anything.

This page reads 164 CVE records that the Apache Software Foundation's CVE Numbering Authority has published since 31 December 2016 and that name Apache Tomcat. 32 of them are not placed on a branch. Of the others, 7 name Apache Tomcat 6.

No release of Apache Tomcat 6 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)