Please note that, except in rare circumstances, binary patches are not
produced for individual vulnerabilities. To obtain the binary fix for a
particular vulnerability you should upgrade to an Apache
Tomcat® version where that vulnerability has been
fixed.
Source patches, usually in the form of references to commits, may be
provided in either in a vulnerability announcement and/or the
vulnerability details listed on these pages. These source patches may be
used by users wishing to build their own local version of Tomcat with just
that security patch rather than upgrade.
Lists of security problems fixed in currently supported versions of
Apache Tomcat are available:
Lists of security problems fixed in versions of Apache Tomcat that have
reached end of life and may be downloaded from the archives are also
available:
The ASF takes a very active stance in eliminating security problems and
denial of service attacks against Tomcat.
We strongly encourage folks to report such problems to our private
security mailing list first, before disclosing them in a public forum.
Please note that the security mailing list should only be used
for reporting undisclosed security vulnerabilities in Tomcat and managing
the process of fixing such vulnerabilities. We cannot accept regular bug
reports, provide free consulting or answer other queries at this address.
All mail sent to this address that does not relate to an undisclosed
security problem in the Tomcat source code will be ignored.
The private security mailing address is:
security@tomcat.apache.org
The Tomcat security model describes
what the Tomcat security team will and will not accept as a valid
vulnerability report for Tomcat.
Note that all networked servers are subject to denial of service attacks,
and we cannot promise magic workarounds to generic problems (such as a
client streaming lots of data to your server, or re-requesting the same
URL repeatedly). In general our philosophy is to avoid any attacks which
can cause the server to consume resources in a non-linear relationship to
the size of inputs.
Questions about:
- how to configure Tomcat securely
- if a vulnerability applies to your particular application
- obtaining further information on a published vulnerability
- availability of patches and/or new releases
should be addressed to the users mailing list. Please see the
mailing lists page for details of how to
subscribe.
If you need to report a bug that isn't an undisclosed security
vulnerability, please use the bug reporting
page.
If you are interested in how reported vulnerabilities are handled, the
process is documented at ASF-wide pages
[1] and
[2].
Please report any errors or omissions to
security@tomcat.apache.org
.
