<?xml version="1.0" encoding="UTF-8"?>
<document>

  <properties>
    <author>Apache Tomcat Project</author>
    <title>Reporting Security Problems</title>
  </properties>

<body>
  <section name="Security Updates">

    <p>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<sup>&#174;</sup> version where that vulnerability has been
       fixed.</p>
       
    <p>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.</p>
       
    <p>Lists of security problems fixed in currently supported versions of
       Apache Tomcat are available:</p>
    <ul>
      <li><a href="security-11.html">Apache Tomcat 11.x Security Vulnerabilities
          </a></li>
      <li><a href="security-10.html">Apache Tomcat 10.x Security Vulnerabilities
          </a></li>
      <li><a href="security-9.html">Apache Tomcat 9.x Security Vulnerabilities
          </a></li>
      <li><a href="security-jk.html">Apache Tomcat JK Connectors Security
          Vulnerabilities</a></li>
      <li><a href="security-native.html">Apache Tomcat APR/native Connector
          Security Vulnerabilities</a></li>
      <li><a href="security-taglibs.html">Apache Taglibs
          Security Vulnerabilities</a></li>
    </ul>

    <p>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:</p>
    <ul>
      <li><a href="security-8.html">Apache Tomcat 8.x Security Vulnerabilities
          </a></li>
      <li><a href="security-7.html">Apache Tomcat 7.x Security Vulnerabilities
          </a></li>
      <li><a href="security-6.html">Apache Tomcat 6.x Security Vulnerabilities
          </a></li>
      <li><a href="security-5.html">Apache Tomcat 5.x Security Vulnerabilities
          </a></li>
      <li><a href="security-4.html">Apache Tomcat 4.x Security Vulnerabilities
          </a></li>
      <li><a href="security-3.html">Apache Tomcat 3.x Security Vulnerabilities
          </a></li>
    </ul>

  </section>

  <section name="Reporting New Security Problems with Tomcat">
    <p>The ASF takes a very active stance in eliminating security problems and
       denial of service attacks against Tomcat.
       </p>

    <p>We strongly encourage folks to report such problems to our private
       security mailing list first, before disclosing them in a public forum.
       </p>

    <p><strong>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.</strong>
       The private security mailing address is:
       <a href="mailto:security@tomcat.apache.org">
       security<span>@</span>tomcat.apache.org</a></p>

    <p>The Tomcat <a href="security-model.html">security model</a> describes
       what the Tomcat security team will and will not accept as a valid
       vulnerability report for Tomcat.</p>
    
    <p>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.</p>

    <p>Questions about:</p>
    <ul>
      <li>how to configure Tomcat securely</li>
      <li>if a vulnerability applies to your particular application</li>
      <li>obtaining further information on a published vulnerability</li>
      <li>availability of patches and/or new releases</li>
    </ul>
    <p>should be addressed to the users mailing list. Please see the
       <a href="lists.html">mailing lists</a> page for details of how to
       subscribe.</p>

    <p>If you need to report a bug that isn't an undisclosed security
       vulnerability, please use the <a href="bugreport.html">bug reporting
       page</a>.</p>
       
    <p>If you are interested in how reported vulnerabilities are handled, the
       process is documented at ASF-wide pages
       <a href="https://apache.org/security/#vulnerability-handling">[1]</a> and
       <a href="https://apache.org/security/committers.html#possible">[2]</a>.
    </p>
  </section>

  <section name="Errors and omissions">

    <p>Please report any errors or omissions to
       <a href="mailto:security@tomcat.apache.org">security@tomcat.apache.org
       </a>.
    </p>

  </section>
</body>
</document>

