tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject svn commit: r1810326 [3/4] - in /tomcat/site/trunk: docs/security-7.html docs/security-8.html docs/security-9.html xdocs/security-7.xml xdocs/security-8.xml xdocs/security-9.xml
Date Mon, 02 Oct 2017 10:01:23 GMT
Modified: tomcat/site/trunk/docs/security-8.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-8.html?rev=1810326&r1=1810325&r2=1810326&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-8.html (original)
+++ tomcat/site/trunk/docs/security-8.html Mon Oct  2 10:01:22 2017
@@ -1,328 +1,331 @@
 <!DOCTYPE html SYSTEM "about:legacy-compat">
 <html lang="en">
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<link href="stylesheets/tomcat.css" rel="stylesheet" type="text/css">
-<title>Apache Tomcat&reg; - Apache Tomcat 8 vulnerabilities</title>
-<meta name="author" content="Apache Tomcat Project">
-</head>
-<body>
-<div id="wrapper">
-<header>
-<div id="header">
-<div>
-<div>
-<div class="logo noPrint">
-<a href="http://tomcat.apache.org/"><img alt="Tomcat Home" src="./images/tomcat.png"></a>
-</div>
-<div style="height: 1px;"></div>
-<div class="asfLogo noPrint">
-<a href="http://apache.org/foundation/contributing.html" target="_blank"><img src="http://www.apache.org/images/SupportApache-small.png" alt="Support Apache" style="height: 83px; margin-right: 15px;"></a><a href="http://www.apache.org/" target="_blank"><img src="./images/asf_logo.svg" alt="The Apache Software Foundation" style="width: 205px; height: 83px; margin-right: 15px;"></a>
-</div>
-<h1 style="margin-top: 35px;">Apache Tomcat<sup>&reg;</sup>
-</h1>
-<div style="clear: right;"></div>
-<div class="searchbox noPrint">
-<form action="https://www.google.com/search" method="get">
-<input value="tomcat.apache.org" name="sitesearch" type="hidden"><input placeholder="Search the Site&hellip;" required="required" size="25" name="q" id="query" type="search"><button>Search</button>
-</form>
-</div>
-<div style="height: 1px;"></div>
-<div style="clear: left;"></div>
-</div>
-</div>
-</div>
-</header>
-<div id="middle">
-<div>
-<div id="mainLeft" class="noprint">
-<div>
-<nav>
-<div>
-<h2>Apache Tomcat</h2>
-<ul>
-<li>
-<a href="./index.html">Home</a>
-</li>
-<li>
-<a href="./taglibs.html">Taglibs</a>
-</li>
-<li>
-<a href="./maven-plugin.html">Maven Plugin</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>TomcatCon</h2>
-<ul>
-<li>
-<a href="./conference.html">London 2017</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Download</h2>
-<ul>
-<li>
-<a href="./whichversion.html">Which version?</a>
-</li>
-<li>
-<a href="./download-90.cgi">Tomcat 9</a>
-</li>
-<li>
-<a href="./download-80.cgi">Tomcat 8</a>
-</li>
-<li>
-<a href="./download-70.cgi">Tomcat 7</a>
-</li>
-<li>
-<a href="./download-connectors.cgi">Tomcat Connectors</a>
-</li>
-<li>
-<a href="./download-native.cgi">Tomcat Native</a>
-</li>
-<li>
-<a href="./download-taglibs.cgi">Taglibs</a>
-</li>
-<li>
-<a href="http://archive.apache.org/dist/tomcat/">Archives</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Documentation</h2>
-<ul>
-<li>
-<a href="./tomcat-9.0-doc/index.html">Tomcat 9.0</a>
-</li>
-<li>
-<a href="./tomcat-8.5-doc/index.html">Tomcat 8.5</a>
-</li>
-<li>
-<a href="./tomcat-8.0-doc/index.html">Tomcat 8.0</a>
-</li>
-<li>
-<a href="./tomcat-7.0-doc/index.html">Tomcat 7.0</a>
-</li>
-<li>
-<a href="./connectors-doc/">Tomcat Connectors</a>
-</li>
-<li>
-<a href="./native-doc/">Tomcat Native</a>
-</li>
-<li>
-<a href="http://wiki.apache.org/tomcat/FrontPage">Wiki</a>
-</li>
-<li>
-<a href="./migration.html">Migration Guide</a>
-</li>
-<li>
-<a href="./presentations.html">Presentations</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Problems?</h2>
-<ul>
-<li>
-<a href="./security.html">Security Reports</a>
-</li>
-<li>
-<a href="./findhelp.html">Find help</a>
-</li>
-<li>
-<a href="http://wiki.apache.org/tomcat/FAQ">FAQ</a>
-</li>
-<li>
-<a href="./lists.html">Mailing Lists</a>
-</li>
-<li>
-<a href="./bugreport.html">Bug Database</a>
-</li>
-<li>
-<a href="./irc.html">IRC</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Get Involved</h2>
-<ul>
-<li>
-<a href="./getinvolved.html">Overview</a>
-</li>
-<li>
-<a href="./svn.html">Source code</a>
-</li>
-<li>
-<a href="./ci.html">Buildbot</a>
-</li>
-<li>
-<a href="./tools.html">Tools</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Media</h2>
-<ul>
-<li>
-<a href="https://twitter.com/theapachetomcat">Twitter</a>
-</li>
-<li>
-<a href="https://www.youtube.com/c/ApacheTomcatOfficial">YouTube</a>
-</li>
-<li>
-<a href="http://blogs.apache.org/tomcat/">Blog</a>
-</li>
-</ul>
-</div>
-<div>
-<h2>Misc</h2>
-<ul>
-<li>
-<a href="./whoweare.html">Who We Are</a>
-</li>
-<li>
-<a href="./heritage.html">Heritage</a>
-</li>
-<li>
-<a href="http://www.apache.org">Apache Home</a>
-</li>
-<li>
-<a href="./resources.html">Resources</a>
-</li>
-<li>
-<a href="./contact.html">Contact</a>
-</li>
-<li>
-<a href="./legal.html">Legal</a>
-</li>
-<li>
-<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
-</li>
-<li>
-<a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
-</li>
-</ul>
-</div>
-</nav>
-</div>
-</div>
-<div id="mainRight">
-<div id="content">
-<h2 style="display: none;">Content</h2>
-<h3 id="Table_of_Contents">Table of Contents</h3>
-<div class="text">
-
-<ul>
-<li>
-<a href="#Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x vulnerabilities</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.47">Fixed in Apache Tomcat 8.0.47</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.23">Fixed in Apache Tomcat 8.5.23</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.45">Fixed in Apache Tomcat 8.0.45</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.16">Fixed in Apache Tomcat 8.5.16</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.44">Fixed in Apache Tomcat 8.0.44</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.15">Fixed in Apache Tomcat 8.5.15</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.43">Fixed in Apache Tomcat 8.0.43</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.13">Fixed in Apache Tomcat 8.5.13</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.42">Fixed in Apache Tomcat 8.0.42</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.12">Fixed in Apache Tomcat 8.5.12</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.41">Fixed in Apache Tomcat 8.0.41</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.11">Fixed in Apache Tomcat 8.5.11</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.9">Fixed in Apache Tomcat 8.5.9</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.39">Fixed in Apache Tomcat 8.0.39</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.8">Fixed in Apache Tomcat 8.5.8</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37">Fixed in Apache Tomcat 8.5.5 and 8.0.37</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.3_and_8.0.36">Fixed in Apache Tomcat 8.5.3 and 8.0.36</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.32">Fixed in Apache Tomcat 8.0.32</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.30">Fixed in Apache Tomcat 8.0.30</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.27">Fixed in Apache Tomcat 8.0.27</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.17">Fixed in Apache Tomcat 8.0.17</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.9">Fixed in Apache Tomcat 8.0.9</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.8">Fixed in Apache Tomcat 8.0.8</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.5">Fixed in Apache Tomcat 8.0.5</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.3">Fixed in Apache Tomcat 8.0.3</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.0-RC10">Fixed in Apache Tomcat 8.0.0-RC10</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_8.0.0-RC3">Fixed in Apache Tomcat 8.0.0-RC3</a>
-</li>
-<li>
-<a href="#Not_a_vulnerability_in_Tomcat">Not a vulnerability in Tomcat</a>
-</li>
-</ul>
-
-</div>
-<h3 id="Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x vulnerabilities</h3>
-<div class="text">
-    
-<p>This page lists all security vulnerabilities fixed in released versions
+    <head>
+        <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+        <link href="stylesheets/tomcat.css" rel="stylesheet" type="text/css">
+        <title>Apache Tomcat&reg; - Apache Tomcat 8 vulnerabilities</title>
+        <meta name="author" content="Apache Tomcat Project">
+    </head>
+    <body>
+        <div id="wrapper">
+            <header>
+                <div id="header">
+                    <div>
+                        <div>
+                            <div class="logo noPrint">
+                                <a href="http://tomcat.apache.org/"><img alt="Tomcat Home" src="./images/tomcat.png"></a>
+                            </div>
+                            <div style="height: 1px;"></div>
+                            <div class="asfLogo noPrint">
+                                <a href="http://apache.org/foundation/contributing.html" target="_blank"><img src="http://www.apache.org/images/SupportApache-small.png" alt="Support Apache" style="height: 83px; margin-right: 15px;"></a><a href="http://www.apache.org/" target="_blank"><img src="./images/asf_logo.svg" alt="The Apache Software Foundation" style="width: 205px; height: 83px; margin-right: 15px;"></a>
+                            </div>
+                            <h1 style="margin-top: 35px;">
+                                Apache Tomcat<sup>&reg;</sup>
+                            </h1>
+                            <div style="clear: right;"></div>
+                            <div class="searchbox noPrint">
+                                <form action="https://www.google.com/search" method="get">
+                                    <input value="tomcat.apache.org" name="sitesearch" type="hidden"><input placeholder="Search the Site&hellip;" required="required" size="25" name="q" id="query" type="search"><button>Search</button>
+                                </form>
+                            </div>
+                            <div style="height: 1px;"></div>
+                            <div style="clear: left;"></div>
+                        </div>
+                    </div>
+                </div>
+            </header>
+            <div id="middle">
+                <div>
+                    <div id="mainLeft" class="noprint">
+                        <div>
+                            <nav>
+                                <div>
+                                    <h2>Apache Tomcat</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./index.html">Home</a>
+                                        </li>
+                                        <li>
+                                            <a href="./taglibs.html">Taglibs</a>
+                                        </li>
+                                        <li>
+                                            <a href="./maven-plugin.html">Maven Plugin</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>TomcatCon</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./conference.html">London 2017</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Download</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./whichversion.html">Which version?</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-90.cgi">Tomcat 9</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-80.cgi">Tomcat 8</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-70.cgi">Tomcat 7</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-connectors.cgi">Tomcat Connectors</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-native.cgi">Tomcat Native</a>
+                                        </li>
+                                        <li>
+                                            <a href="./download-taglibs.cgi">Taglibs</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://archive.apache.org/dist/tomcat/">Archives</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Documentation</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./tomcat-9.0-doc/index.html">Tomcat 9.0</a>
+                                        </li>
+                                        <li>
+                                            <a href="./tomcat-8.5-doc/index.html">Tomcat 8.5</a>
+                                        </li>
+                                        <li>
+                                            <a href="./tomcat-8.0-doc/index.html">Tomcat 8.0</a>
+                                        </li>
+                                        <li>
+                                            <a href="./tomcat-7.0-doc/index.html">Tomcat 7.0</a>
+                                        </li>
+                                        <li>
+                                            <a href="./connectors-doc/">Tomcat Connectors</a>
+                                        </li>
+                                        <li>
+                                            <a href="./native-doc/">Tomcat Native</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://wiki.apache.org/tomcat/FrontPage">Wiki</a>
+                                        </li>
+                                        <li>
+                                            <a href="./migration.html">Migration Guide</a>
+                                        </li>
+                                        <li>
+                                            <a href="./presentations.html">Presentations</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Problems?</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./security.html">Security Reports</a>
+                                        </li>
+                                        <li>
+                                            <a href="./findhelp.html">Find help</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://wiki.apache.org/tomcat/FAQ">FAQ</a>
+                                        </li>
+                                        <li>
+                                            <a href="./lists.html">Mailing Lists</a>
+                                        </li>
+                                        <li>
+                                            <a href="./bugreport.html">Bug Database</a>
+                                        </li>
+                                        <li>
+                                            <a href="./irc.html">IRC</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Get Involved</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./getinvolved.html">Overview</a>
+                                        </li>
+                                        <li>
+                                            <a href="./svn.html">Source code</a>
+                                        </li>
+                                        <li>
+                                            <a href="./ci.html">Buildbot</a>
+                                        </li>
+                                        <li>
+                                            <a href="./tools.html">Tools</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Media</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="https://twitter.com/theapachetomcat">Twitter</a>
+                                        </li>
+                                        <li>
+                                            <a href="https://www.youtube.com/c/ApacheTomcatOfficial">YouTube</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://blogs.apache.org/tomcat/">Blog</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                                <div>
+                                    <h2>Misc</h2>
+                                    <ul>
+                                        <li>
+                                            <a href="./whoweare.html">Who We Are</a>
+                                        </li>
+                                        <li>
+                                            <a href="./heritage.html">Heritage</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://www.apache.org">Apache Home</a>
+                                        </li>
+                                        <li>
+                                            <a href="./resources.html">Resources</a>
+                                        </li>
+                                        <li>
+                                            <a href="./contact.html">Contact</a>
+                                        </li>
+                                        <li>
+                                            <a href="./legal.html">Legal</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+                                        </li>
+                                        <li>
+                                            <a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
+                                        </li>
+                                    </ul>
+                                </div>
+                            </nav>
+                        </div>
+                    </div>
+                    <div id="mainRight">
+                        <div id="content">
+                            <h2 style="display: none;">Content</h2>
+                            <h3 id="Table_of_Contents">Table of Contents</h3>
+                            <div class="text">
+                                
+                                <ul>
+                                    <li>
+                                        <a href="#Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x vulnerabilities</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.47">Fixed in Apache Tomcat 8.0.47</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.23">Fixed in Apache Tomcat 8.5.23</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.45">Fixed in Apache Tomcat 8.0.45</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.16">Fixed in Apache Tomcat 8.5.16</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.44">Fixed in Apache Tomcat 8.0.44</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.15">Fixed in Apache Tomcat 8.5.15</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.43">Fixed in Apache Tomcat 8.0.43</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.13">Fixed in Apache Tomcat 8.5.13</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.42">Fixed in Apache Tomcat 8.0.42</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.12">Fixed in Apache Tomcat 8.5.12</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.41">Fixed in Apache Tomcat 8.0.41</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.11">Fixed in Apache Tomcat 8.5.11</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.9">Fixed in Apache Tomcat 8.5.9</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.39">Fixed in Apache Tomcat 8.0.39</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.8">Fixed in Apache Tomcat 8.5.8</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37">Fixed in Apache Tomcat 8.5.5 and 8.0.37</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.5.3_and_8.0.36">Fixed in Apache Tomcat 8.5.3 and 8.0.36</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.32">Fixed in Apache Tomcat 8.0.32</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.30">Fixed in Apache Tomcat 8.0.30</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.27">Fixed in Apache Tomcat 8.0.27</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.17">Fixed in Apache Tomcat 8.0.17</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.9">Fixed in Apache Tomcat 8.0.9</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.8">Fixed in Apache Tomcat 8.0.8</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.5">Fixed in Apache Tomcat 8.0.5</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.3">Fixed in Apache Tomcat 8.0.3</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.0-RC10">Fixed in Apache Tomcat 8.0.0-RC10</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Fixed_in_Apache_Tomcat_8.0.0-RC3">Fixed in Apache Tomcat 8.0.0-RC3</a>
+                                    </li>
+                                    <li>
+                                        <a href="#Not_a_vulnerability_in_Tomcat">Not a vulnerability in Tomcat</a>
+                                    </li>
+                                </ul>
+                                
+                            </div>
+                            <h3 id="Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x vulnerabilities</h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    This page lists all security vulnerabilities fixed in released versions
        of Apache Tomcat 8.x. Each vulnerability is given a
        <a href="security-impact.html">security impact rating</a> by the Apache
        Tomcat security team &mdash; please note that this rating may vary from
        platform to platform. We also list the versions of Apache Tomcat the flaw
        is known to affect, and where a flaw has not been verified list the
-       version with a question mark.</p>
-
-    
-<p>
-<strong>Note:</strong> Vulnerabilities that are not Tomcat vulnerabilities
+       version with a question mark.
+                                </p>
+                                    
+                                <p>
+                                    <strong>Note:</strong> Vulnerabilities that are not Tomcat vulnerabilities
        but have either been incorrectly reported against Tomcat or where Tomcat
-       provides a workaround are listed at the end of this page.</p>
-
-    
-<p>Please note that binary patches are never provided. If you need to
+       provides a workaround are listed at the end of this page.
+                                </p>
+                                    
+                                <p>
+                                    Please note that binary patches are never provided. If you need to
        apply a source code patch, use the building instructions for the
        Apache Tomcat version that you are using. For Tomcat 8.0 those are
        <a href="/tomcat-8.0-doc/building.html"><code>building.html</code></a> and
@@ -330,882 +333,815 @@
        Both files can be found in the <code>webapps/docs</code> subdirectory
        of a binary distributive. You may also want to review the
        <a href="/tomcat-8.0-doc/security-howto.html">Security Considerations</a>
-       page in the documentation.</p>
-
-    
-<p>If you need help on building or configuring Tomcat or other help on
+       page in the documentation.
+                                </p>
+                                    
+                                <p>
+                                    If you need help on building or configuring Tomcat or other help on
        following the instructions to mitigate the known vulnerabilities listed
        here, please send your questions to the public
        <a href="lists.html">Tomcat Users mailing list</a>
     
-</p>
-
-    
-<p>If you have encountered an unlisted security vulnerability or other
+                                </p>
+                                    
+                                <p>
+                                    If you have encountered an unlisted security vulnerability or other
        unexpected behaviour that has <a href="security-impact.html">security
        impact</a>, or if the descriptions here are incomplete,
        please report them privately to the
        <a href="security.html">Tomcat Security Team</a>. Thank you.
-    </p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.47">
-<span style="float: right;">TBD October 2017</span> Fixed in Apache Tomcat 8.0.47</h3>
-<div class="text">
-
     
-<p>
-<strong>Important: Remote Code Execution</strong>
+                                </p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.47">
+                                <span style="float: right;">TBD October 2017</span> Fixed in Apache Tomcat 8.0.47
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Remote Code Execution</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617" rel="nofollow">CVE-2017-12617</a>
-</p>
-
-    
-<p>When running on Windows with HTTP PUTs enabled (e.g. via setting the
+                                </p>
+                                    
+                                <p>
+                                    When running with HTTP PUTs enabled (e.g. via setting the
        <code>readonly</code> initialisation parameter of the Default to false)
        it was possible to upload a JSP file to the server via a specially
        crafted request. This JSP could then be requested and any code it
-       contained would be executed by the server.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809921">1809921</a>.</p>
-
-    
-<p>This issue was first reported publicly followed by multiple reports to
+       contained would be executed by the server.
+                                </p>
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809921">1809921</a>.
+                                </p>
+                                    
+                                <p>This issue was first reported publicly followed by multiple reports to
        the Apache Tomcat Security Team on 20 September 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.46</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.23">
-<span style="float: right;">1 October 2017</span> Fixed in Apache Tomcat 8.5.23</h3>
-<div class="text">
-
-    
-<p>
-<strong>Important: Remote Code Execution</strong>
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.46</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.23">
+                                <span style="float: right;">1 October 2017</span> Fixed in Apache Tomcat 8.5.23
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Remote Code Execution</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617" rel="nofollow">CVE-2017-12617</a>
-</p>
-
-    
-<p>When running on Windows with HTTP PUTs enabled (e.g. via setting the
+                                </p>
+                                    
+                                <p>
+                                    When running with HTTP PUTs enabled (e.g. via setting the
        <code>readonly</code> initialisation parameter of the Default to false)
        it was possible to upload a JSP file to the server via a specially
        crafted request. This JSP could then be requested and any code it
-       contained would be executed by the server.</p>
-
-    
-<p>This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809673">1809673</a>,
+       contained would be executed by the server.
+                                </p>
+                                    
+                                <p>
+                                    This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809673">1809673</a>,
        <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809675">1809675</a> and
-       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809896">1809896</a>.</p>
-
-    
-<p>This issue was first reported publicly followed by multiple reports to
+       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1809896">1809896</a>.
+                                </p>
+                                    
+                                <p>This issue was first reported publicly followed by multiple reports to
        the Apache Tomcat Security Team on 20 September 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.22</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.45">
-<span style="float: right;">1 July 2017</span> Fixed in Apache Tomcat 8.0.45</h3>
-<div class="text">
-
-    
-<p>
-<strong>Moderate: Cache Poisoning</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.22</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.45">
+                                <span style="float: right;">1 July 2017</span> Fixed in Apache Tomcat 8.0.45
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Moderate: Cache Poisoning</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7674" rel="nofollow">CVE-2017-7674</a>
-</p>
-
-    
-<p>The CORS Filter did not add an HTTP Vary header indicating that the
+                                </p>
+                                    
+                                <p>The CORS Filter did not add an HTTP Vary header indicating that the
        response varies depending on Origin. This permitted client and server
        side cache poisoning in some circumstances.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1795815">1795815</a>.</p>
-
-    
-<p>The issue was reported as bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61101">61101</a> on 16 May 2017. The full
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1795815">1795815</a>.
+                                </p>
+                                    
+                                <p>
+                                    The issue was reported as bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61101">61101</a> on 16 May 2017. The full
        implications of this issue were identified by the Tomcat Security Team
-       the same day. This issue was made public on 10 August 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.44</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.16">
-<span style="float: right;">26 June 2017</span> Fixed in Apache Tomcat 8.5.16</h3>
-<div class="text">
-
-    
-<p>
-<strong>Important: Security Constraint Bypass</strong>
+       the same day. This issue was made public on 10 August 2017.
+                                </p>
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.44</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.16">
+                                <span style="float: right;">26 June 2017</span> Fixed in Apache Tomcat 8.5.16
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Security Constraint Bypass</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7675" rel="nofollow">CVE-2017-7675</a>
-</p>
-
-    
-<p>The HTTP/2 implementation bypassed a number of security checks that
+                                </p>
+                                    
+                                <p>The HTTP/2 implementation bypassed a number of security checks that
        prevented directory traversal attacks. It was therefore possible to
        bypass security constraints using an specially crafted URL.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1796091">1796091</a>.</p>
-
-    
-<p>The issue was originally reported as a failure to process URL path
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1796091">1796091</a>.
+                                </p>
+                                    
+                                <p>
+                                    The issue was originally reported as a failure to process URL path
        parameters in bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61120">61120</a> on 24 May 2017. The full implications
        of this issue were identified by the Tomcat Security Team the same day.
-       This issue was made public on 10 August 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.15</p>
-
-    
-<p>
-<strong>Moderate: Cache Poisoning</strong>
+       This issue was made public on 10 August 2017.
+                                </p>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.15</p>
+                                    
+                                <p>
+                                    <strong>Moderate: Cache Poisoning</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7674" rel="nofollow">CVE-2017-7674</a>
-</p>
-
-    
-<p>The CORS Filter did not add an HTTP Vary header indicating that the
+                                </p>
+                                    
+                                <p>The CORS Filter did not add an HTTP Vary header indicating that the
        response varies depending on Origin. This permitted client and server
        side cache poisoning in some circumstances.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1795814">1795814</a>.</p>
-
-    
-<p>The issue was reported as bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61101">61101</a> on 16 May 2017. The full
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1795814">1795814</a>.
+                                </p>
+                                    
+                                <p>
+                                    The issue was reported as bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61101">61101</a> on 16 May 2017. The full
        implications of this issue were identified by the Tomcat Security Team
-       the same day. This issue was made public on 10 August 2017.</p>
-
+       the same day. This issue was made public on 10 August 2017.
+                                </p>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.15</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.44">
+                                <span style="float: right;">16 May 2017</span> Fixed in Apache Tomcat 8.0.44
+                            </h3>
+                            <div class="text">
+                                  
     
-<p>Affects: 8.5.0 to 8.5.15</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.44">
-<span style="float: right;">16 May 2017</span> Fixed in Apache Tomcat 8.0.44</h3>
-<div class="text">
-  
-    
-<p>
-<strong>Important: Security Constraint Bypass</strong>
+                                <p>
+                                    <strong>Important: Security Constraint Bypass</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664" rel="nofollow">CVE-2017-5664</a>
-</p>
-
-    
-<p>The error page mechanism of the Java Servlet Specification requires that,
+                                </p>
+                                    
+                                <p>The 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 forwarded to the error
        page. This means that the request is presented to the error page with the
        original HTTP method.</p>
-
-   
-<p>If the error page is a static file, expected behaviour is to serve content
+                                   
+                                <p>If the error page is a static file, expected behaviour is to serve content
       of the file as if processing a GET request, regardless of the actual HTTP
       method. Tomcat's Default Servlet did not do this. Depending on the
       original request this could lead to unexpected and undesirable results for
       static error pages including, if the DefaultServlet is configured to
       permit writes, the replacement or removal of the custom error page.</p>
-
-    
-<p>Notes for other user provided error pages:</p>
-    
-<ul>
-      
-<li>Unless explicitly coded otherwise, JSPs ignore the HTTP method.
+                                    
+                                <p>Notes for other user provided error pages:</p>
+                                    
+                                <ul>
+                                          
+                                    <li>Unless explicitly coded otherwise, JSPs ignore the HTTP method.
           JSPs used as error pages must ensure that they handle any error
           dispatch as a GET request, regardless of the actual method.</li>
-      
-<li>By default, the response generated by a Servlet does depend on the
+                                          
+                                    <li>By default, the response generated by a Servlet does depend on the
           HTTP method. Custom Servlets used as error pages must ensure that
           they handle any error dispatch as a GET request, regardless of the
           actual method.</li>
-    
-</ul>
-
-    
-<p>This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793470">1793470</a> and
-       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793489">1793489</a>.</p>
-
-    
-<p>This issue was reported responsibly to the Apache Tomcat Security Team by
+                                        
+                                </ul>
+                                    
+                                <p>
+                                    This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793470">1793470</a> and
+       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793489">1793489</a>.
+                                </p>
+                                    
+                                <p>This issue was reported responsibly to the Apache Tomcat Security Team by
        Aniket Nandkishor Kulkarni from Tata Consultancy Services Ltd, Mumbai,
        India as a vulnerability that allowed the restrictions on OPTIONS and
        TRACE requests to be bypassed on 21 April 2017. The full implications of
        this issue were identified by the Tomcat Security Team on 24 April 2017.
        This issue was made public on 6 June 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.43</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.15">
-<span style="float: right;">10 May 2017</span> Fixed in Apache Tomcat 8.5.15</h3>
-<div class="text">
-  
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.43</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.15">
+                                <span style="float: right;">10 May 2017</span> Fixed in Apache Tomcat 8.5.15
+                            </h3>
+                            <div class="text">
+                                  
     
-<p>
-<strong>Important: Security Constraint Bypass</strong>
+                                <p>
+                                    <strong>Important: Security Constraint Bypass</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664" rel="nofollow">CVE-2017-5664</a>
-</p>
-
-    
-<p>The error page mechanism of the Java Servlet Specification requires that,
+                                </p>
+                                    
+                                <p>The 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 forwarded to the error
        page. This means that the request is presented to the error page with the
        original HTTP method.</p>
-
-   
-<p>If the error page is a static file, expected behaviour is to serve content
+                                   
+                                <p>If the error page is a static file, expected behaviour is to serve content
       of the file as if processing a GET request, regardless of the actual HTTP
       method. Tomcat's Default Servlet did not do this. Depending on the
       original request this could lead to unexpected and undesirable results for
       static error pages including, if the DefaultServlet is configured to
       permit writes, the replacement or removal of the custom error page.</p>
-
-    
-<p>Notes for other user provided error pages:</p>
-    
-<ul>
-      
-<li>Unless explicitly coded otherwise, JSPs ignore the HTTP method.
+                                    
+                                <p>Notes for other user provided error pages:</p>
+                                    
+                                <ul>
+                                          
+                                    <li>Unless explicitly coded otherwise, JSPs ignore the HTTP method.
           JSPs used as error pages must ensure that they handle any error
           dispatch as a GET request, regardless of the actual method.</li>
-      
-<li>By default, the response generated by a Servlet does depend on the
+                                          
+                                    <li>By default, the response generated by a Servlet does depend on the
           HTTP method. Custom Servlets used as error pages must ensure that
           they handle any error dispatch as a GET request, regardless of the
           actual method.</li>
-    
-</ul>
-
-    
-<p>This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793469">1793469</a> and
-       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793488">1793488</a>.</p>
-
-    
-<p>This issue was reported responsibly to the Apache Tomcat Security Team by
+                                        
+                                </ul>
+                                    
+                                <p>
+                                    This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793469">1793469</a> and
+       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1793488">1793488</a>.
+                                </p>
+                                    
+                                <p>This issue was reported responsibly to the Apache Tomcat Security Team by
        Aniket Nandkishor Kulkarni from Tata Consultancy Services Ltd, Mumbai,
        India as a vulnerability that allowed the restrictions on OPTIONS and
        TRACE requests to be bypassed on 21 April 2017. The full implications of
        this issue were identified by the Tomcat Security Team on 24 April 2017.
        This issue was made public on 6 June 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.14</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.43">
-<span style="float: right;">2 April 2017</span> Fixed in Apache Tomcat 8.0.43</h3>
-<div class="text">
-
-  
-<p>
-<strong>Important: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.14</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.43">
+                                <span style="float: right;">2 April 2017</span> Fixed in Apache Tomcat 8.0.43
+                            </h3>
+                            <div class="text">
+                                  
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647" rel="nofollow">CVE-2017-5647</a>
-</p>
-
-    
-<p>A bug in the handling of the pipelined requests when send file was used
+                                </p>
+                                    
+                                <p>A bug in the handling of the pipelined requests when send file was used
        resulted 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.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788999">1788999</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788999">1788999</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 20
        March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.42</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.13">
-<span style="float: right;">30 March 2017</span> Fixed in Apache Tomcat 8.5.13</h3>
-<div class="text">
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.42</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.13">
+                                <span style="float: right;">30 March 2017</span> Fixed in Apache Tomcat 8.5.13
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651" rel="nofollow">CVE-2017-5651</a>
-</p>
-
-    
-<p>The refactoring of the HTTP connectors for 8.5.x onwards, introduced a
+                                </p>
+                                    
+                                <p>The refactoring of the HTTP connectors for 8.5.x onwards, 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.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788546">1788546</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 24
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788546">1788546</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 24
        March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.12</p>
-
-    
-<p>
-<strong>Important: Denial of Service</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.12</p>
+                                    
+                                <p>
+                                    <strong>Important: Denial of Service</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650" rel="nofollow">CVE-2017-5650</a>
-</p>
-
-    
-<p>The handling of an HTTP/2 GOAWAY frame for a connection did not close
+                                </p>
+                                    
+                                <p>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.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788480">1788480</a>.</p>
-
-    
-<p>This issue was reported to the Apache Tomcat Security Team by Chun Han
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788480">1788480</a>.
+                                </p>
+                                    
+                                <p>This issue was reported to the Apache Tomcat Security Team by Chun Han
        Hsiao on 11 March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.12</p>
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.12</p>
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647" rel="nofollow">CVE-2017-5647</a>
-</p>
-
-    
-<p>A bug in the handling of the pipelined requests when send file was used
+                                </p>
+                                    
+                                <p>A bug in the handling of the pipelined requests when send file was used
        resulted 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.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788932">1788932</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1788932">1788932</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 20
        March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.12</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.42">
-<span style="float: right;">14 March 2017</span> Fixed in Apache Tomcat 8.0.42</h3>
-<div class="text">
-
-  
-<p>
-<strong>Low: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.12</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.42">
+                                <span style="float: right;">14 March 2017</span> Fixed in Apache Tomcat 8.0.42
+                            </h3>
+                            <div class="text">
+                                  
+                                <p>
+                                    <strong>Low: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648" rel="nofollow">CVE-2017-5648</a>
-</p>
-
-    
-<p>While investigating bug 60718, it was noticed that some calls to
+                                </p>
+                                    
+                                <p>While investigating bug 60718, it was noticed that some calls to
        application listeners did not use the appropriate facade object. When
        running an untrusted application under a SecurityManager, it was
        therefore possible for that untrusted application to retain a reference
        to the request or response object and thereby access and/or modify
        information associated with another web application.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1785776">1785776</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1785776">1785776</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 20
        March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.41</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.12">
-<span style="float: right;">13 March 2017</span> Fixed in Apache Tomcat 8.5.12</h3>
-<div class="text">
-
-  
-<p>
-<strong>Low: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.41</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.12">
+                                <span style="float: right;">13 March 2017</span> Fixed in Apache Tomcat 8.5.12
+                            </h3>
+                            <div class="text">
+                                  
+                                <p>
+                                    <strong>Low: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648" rel="nofollow">CVE-2017-5648</a>
-</p>
-
-    
-<p>While investigating bug 60718, it was noticed that some calls to
+                                </p>
+                                    
+                                <p>While investigating bug 60718, it was noticed that some calls to
        application listeners did not use the appropriate facade object. When
        running an untrusted application under a SecurityManager, it was
        therefore possible for that untrusted application to retain a reference
        to the request or response object and thereby access and/or modify
        information associated with another web application.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1785775">1785775</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1785775">1785775</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 20
        March 2017 and made public on 10 April 2017.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.11</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.41">
-<span style="float: right;">24 January 2017</span> Fixed in Apache Tomcat 8.0.41</h3>
-<div class="text">
-
-    
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 8.0.40 but the
+                                    
+                                <p>Affects: 8.5.0 to 8.5.11</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.41">
+                                <span style="float: right;">24 January 2017</span> Fixed in Apache Tomcat 8.0.41
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <i>Note: The issue below was fixed in Apache Tomcat 8.0.40 but the
        release vote for the 8.0.40 release candidate did not pass. Therefore,
        although users must download 8.0.41 to obtain a version that includes
        the fix for this issue, version 8.0.40 is not included in the list of
        affected versions.</i>
-</p>
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+                                </p>
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8745" rel="nofollow">CVE-2016-8745</a>
-</p>
-
-    
-<p>A bug in the error handling of the send file code for the NIO HTTP
+                                </p>
+                                    
+                                <p>A bug in the error handling of the send file code for the NIO HTTP
        connector resulted in the current Processor object being added to the
        Processor cache multiple times. This in turn meant that the same
        Processor could be used for concurrent requests. Sharing a Processor can
        result in information leakage between requests including, but not limited
        to, session ID and the response body.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1777469">1777469</a>.</p>
-
-    
-<p>This issue was identified as affecting 8.0.x by the Apache Tomcat Security
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1777469">1777469</a>.
+                                </p>
+                                    
+                                <p>This issue was identified as affecting 8.0.x by the Apache Tomcat Security
        Team on 3 January 2016 and made public on 5 January 2017.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.39</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.11">
-<span style="float: right;">16 January 2017</span> Fixed in Apache Tomcat 8.5.11</h3>
-<div class="text">
-
-    
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 8.5.10 but the
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.39</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.11">
+                                <span style="float: right;">16 January 2017</span> Fixed in Apache Tomcat 8.5.11
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <i>Note: The issue below was fixed in Apache Tomcat 8.5.10 but the
        release vote for the 8.5.10 release candidate did not pass. Therefore,
        although users must download 8.5.11 to obtain a version that includes
        the fix for this issue, version 8.5.10 is not included in the list of
        affected versions.</i>
-</p>
-
-  
-<p>
-<strong>Moderate: Information Disclosure</strong>
+                                </p>
+                                  
+                                <p>
+                                    <strong>Moderate: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8747" rel="nofollow">CVE-2016-8747</a>
-</p>
-
-    
-<p>The refactoring to make wider use of ByteBuffer introduced a regression
+                                </p>
+                                    
+                                <p>The refactoring to make wider use of ByteBuffer introduced a regression
        that could cause information to leak between requests on the same
        connection. When running behind a reverse proxy, this could result in
        information leakage between users. All HTTP connector variants are
        affected but HTTP/2 and AJP are not affected.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1774166">1774166</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 14
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1774166">1774166</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 14
        December 2016 and made public on 13 March 2017.</p>
-
-    
-<p>Affects: 8.5.7 to 8.5.9</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.9">
-<span style="float: right;">8 December 2016</span> Fixed in Apache Tomcat 8.5.9</h3>
-<div class="text">
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.5.7 to 8.5.9</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.9">
+                                <span style="float: right;">8 December 2016</span> Fixed in Apache Tomcat 8.5.9
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8745" rel="nofollow">CVE-2016-8745</a>
-</p>
-
-    
-<p>A bug in the error handling of the send file code for the NIO HTTP
+                                </p>
+                                    
+                                <p>A bug in the error handling of the send file code for the NIO HTTP
        connector resulted in the current Processor object being added to the
        Processor cache multiple times. This in turn meant that the same
        Processor could be used for concurrent requests. Sharing a Processor can
        result in information leakage between requests including, but not limited
        to, session ID and the response body.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1771857">1771857</a>.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 8 December
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1771857">1771857</a>.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 8 December
        2016 and made public on 12 December 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.8</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.0.39">
-<span style="float: right;">14 November 2016</span> Fixed in Apache Tomcat 8.0.39</h3>
-<div class="text">
-
-    
-<p>
-<strong>Important: Remote Code Execution</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.8</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.0.39">
+                                <span style="float: right;">14 November 2016</span> Fixed in Apache Tomcat 8.0.39
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <strong>Important: Remote Code Execution</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8735" rel="nofollow">CVE-2016-8735</a>
-</p>
-
-    
-<p>The <code>JmxRemoteLifecycleListener</code> was not updated to take
+                                </p>
+                                    
+                                <p>
+                                    The <code>JmxRemoteLifecycleListener</code> was not updated to take
        account of Oracle's fix for <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3427" rel="nofollow">CVE-2016-3427</a>. Therefore, Tomcat
        installations using this listener remained vulnerable to a similar remote
        code execution vulnerability. This issue has been rated as important
        rather than critical due to the small number of installations using this
        listener and that it would be highly unusual for the JMX ports to be
-       accessible to an attacker even when the listener is used.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767656">1767656</a>.</p>
-
-    
-<p>This issue was reported to the Apache Tomcat Security Team on 19 October
+       accessible to an attacker even when the listener is used.
+                                </p>
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767656">1767656</a>.
+                                </p>
+                                    
+                                <p>This issue was reported to the Apache Tomcat Security Team on 19 October
        2016 and made public on 22 November 2016.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.38</p>
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.38</p>
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816" rel="nofollow">CVE-2016-6816</a>
-</p>
-
-    
-<p>The code that parsed the HTTP request line permitted invalid characters.
+                                </p>
+                                    
+                                <p>The code that parsed the HTTP request line permitted invalid characters.
        This could be exploited, in conjunction with a proxy that also permitted
        the invalid characters but with a different interpretation, to inject
        data into the HTTP response. By manipulating the HTTP response the
        attacker could poison a web-cache, perform an XSS attack and/or obtain
        sensitive information from requests other then their own.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767653">1767653</a>.</p>
-
-    
-<p>This issue was reported to the Apache Tomcat Security Team on 11
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767653">1767653</a>.
+                                </p>
+                                    
+                                <p>This issue was reported to the Apache Tomcat Security Team on 11
        October 2016 and made public on 22 November 2016.</p>
-
-    
-<p>Affects: 8.0.0.RC1 to 8.0.38</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.8">
-<span style="float: right;">8 November 2016</span> Fixed in Apache Tomcat 8.5.8</h3>
-<div class="text">
-
-    
-<p>
-<i>Note: The issues below were fixed in Apache Tomcat 8.5.7 but the
+                                    
+                                <p>Affects: 8.0.0.RC1 to 8.0.38</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.8">
+                                <span style="float: right;">8 November 2016</span> Fixed in Apache Tomcat 8.5.8
+                            </h3>
+                            <div class="text">
+                                    
+                                <p>
+                                    <i>Note: The issues below were fixed in Apache Tomcat 8.5.7 but the
        release vote for the 8.5.7 release candidate did not pass. Therefore,
        although users must download 8.5.8 to obtain a version that includes
        fixes for these issues, version 8.5.7 is not included in the list of
        affected versions.</i>
-</p>
-  
+                                </p>
+                                  
     
-<p>
-<strong>Important: Remote Code Execution</strong>
+                                <p>
+                                    <strong>Important: Remote Code Execution</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8735" rel="nofollow">CVE-2016-8735</a>
-</p>
-
-    
-<p>The <code>JmxRemoteLifecycleListener</code> was not updated to take
+                                </p>
+                                    
+                                <p>
+                                    The <code>JmxRemoteLifecycleListener</code> was not updated to take
        account of Oracle's fix for <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3427" rel="nofollow">CVE-2016-3427</a>. Therefore, Tomcat
        installations using this listener remained vulnerable to a similar remote
        code execution vulnerability. This issue has been rated as important
        rather than critical due to the small number of installations using this
        listener and that it would be highly unusual for the JMX ports to be
-       accessible to an attacker even when the listener is used.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767646">1767646</a>.</p>
-
-    
-<p>This issue was reported to the Apache Tomcat Security Team on 19 October
+       accessible to an attacker even when the listener is used.
+                                </p>
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767646">1767646</a>.
+                                </p>
+                                    
+                                <p>This issue was reported to the Apache Tomcat Security Team on 19 October
        2016 and made public on 22 November 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.6</p>
-
-    
-<p>
-<strong>Important: Denial of Service</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.6</p>
+                                    
+                                <p>
+                                    <strong>Important: Denial of Service</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6817" rel="nofollow">CVE-2016-6817</a>
-</p>
-
-    
-<p>The HTTP/2 header parser entered an infinite loop if a header was
+                                </p>
+                                    
+                                <p>The HTTP/2 header parser entered an infinite loop if a header was
        received that was larger than the available buffer. This made a denial of
        service attack possible.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1765798">1765798</a>.</p>
-
-    
-<p>This issue was reported as <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60232">60232</a> on 10 October 2016 and the
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1765798">1765798</a>.
+                                </p>
+                                    
+                                <p>
+                                    This issue was reported as <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60232">60232</a> on 10 October 2016 and the
        security implications identified by the Apache Tomcat Security Team on
-       the same day. It was made public on 22 November 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.6</p>
-
-    
-<p>
-<strong>Important: Information Disclosure</strong>
+       the same day. It was made public on 22 November 2016.
+                                </p>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.6</p>
+                                    
+                                <p>
+                                    <strong>Important: Information Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816" rel="nofollow">CVE-2016-6816</a>
-</p>
-
-    
-<p>The code that parsed the HTTP request line permitted invalid characters.
+                                </p>
+                                    
+                                <p>The code that parsed the HTTP request line permitted invalid characters.
        This could be exploited, in conjunction with a proxy that also permitted
        the invalid characters but with a different interpretation, to inject
        data into the HTTP response. By manipulating the HTTP response the
        attacker could poison a web-cache, perform an XSS attack and/or obtain
        sensitive information from requests other then their own.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767645">1767645</a>.</p>
-
-    
-<p>This issue was reported to the Apache Tomcat Security Team on 11
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1767645">1767645</a>.
+                                </p>
+                                    
+                                <p>This issue was reported to the Apache Tomcat Security Team on 11
        October 2016 and made public on 22 November 2016.</p>
-
+                                    
+                                <p>Affects: 8.5.0 to 8.5.6</p>
+                                  
+                            </div>
+                            <h3 id="Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37">
+                                <span style="float: right;">5 September 2016</span> Fixed in Apache Tomcat 8.5.5 and 8.0.37
+                            </h3>
+                            <div class="text">
+                                  
     
-<p>Affects: 8.5.0 to 8.5.6</p>
-
-  
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37">
-<span style="float: right;">5 September 2016</span> Fixed in Apache Tomcat 8.5.5 and 8.0.37</h3>
-<div class="text">
-  
-    
-<p>
-<strong>Low: Unrestricted Access to Global Resources</strong>
+                                <p>
+                                    <strong>Low: Unrestricted Access to Global Resources</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797" rel="nofollow">CVE-2016-6797</a>
-</p>
-
-    
-<p>The ResourceLinkFactory did not limit web application access to global
+                                </p>
+                                    
+                                <p>The ResourceLinkFactory did not limit web application access to global
        JNDI resources to those resources explicitly linked to the web
        application. Therefore, it was possible for a web application to access
        any global JNDI resource whether an explicit ResourceLink had been
        configured or not.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1757272">1757272</a> for
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1757272">1757272</a> for
        8.5.x and revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1757273">1757273</a> for
-       8.0.x.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 18
+       8.0.x.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 18
        January 2016 and made public on 27 October 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
-
-    
-<p>
-<strong>Low: Security Manager Bypass</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
+                                    
+                                <p>
+                                    <strong>Low: Security Manager Bypass</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6796" rel="nofollow">CVE-2016-6796</a>
-</p>
-
-    
-<p>A malicious web application was able to bypass a configured
+                                </p>
+                                    
+                                <p>A malicious web application was able to bypass a configured
        SecurityManager via manipulation of the configuration parameters for the
        JSP Servlet.</p>
-
-    
-<p>This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1758493">1758493</a> and
+                                    
+                                <p>
+                                    This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1758493">1758493</a> and
        <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1763233">1763233</a> for 8.5.x and revisions
        <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1758494">1758494</a> and
-       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1763234">1763234</a>for 8.0.x.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 27
+       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1763234">1763234</a>for 8.0.x.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 27
        December 2015 and made public on 27 October 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
-
-    
-<p>
-<strong>Low: System Property Disclosure</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
+                                    
+                                <p>
+                                    <strong>Low: System Property Disclosure</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6794" rel="nofollow">CVE-2016-6794</a>
-</p>
-
-    
-<p>When a SecurityManager is configured, a web application's ability to read
+                                </p>
+                                    
+                                <p>When a SecurityManager is configured, a web application's ability to read
        system properties should be controlled by the SecurityManager. Tomcat's
        system property replacement feature for configuration files could be used
        by a malicious web application to bypass the SecurityManager and read
        system properties that should not be visible.</p>
-
-    
-<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754726">1754726</a> for
+                                    
+                                <p>
+                                    This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754726">1754726</a> for
        8.5.x and revision <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754727">1754727</a> for
-       8.0.x.</p>
-
-    
-<p>This issue was identified by the Apache Tomcat Security Team on 27
+       8.0.x.
+                                </p>
+                                    
+                                <p>This issue was identified by the Apache Tomcat Security Team on 27
        December 2015 and made public on 27 October 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
-
-    
-<p>
-<strong>Low: Security Manager Bypass</strong>
+                                    
+                                <p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
+                                    
+                                <p>
+                                    <strong>Low: Security Manager Bypass</strong>
        <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5018" rel="nofollow">CVE-2016-5018</a>
-</p>
-
-    
-<p>A malicious web application was able to bypass a configured
+                                </p>
+                                    
+                                <p>A malicious web application was able to bypass a configured
        SecurityManager via a Tomcat utility method that was accessible to web
        applications.</p>
-
-    
-<p>This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754900">1754900</a> and
+                                    
+                                <p>
+                                    This was fixed in revisions <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754900">1754900</a> and
        <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1760305">1760305</a> for 8.5.x and revisions
        <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1754901">1754901</a> and
-       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1760307">1760307</a> for 8.0.x.</p>
-
-    
-<p>This issue was discovered by Alvaro Munoz and Alexander Mirosh of the HP
+       <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1760307">1760307</a> for 8.0.x.
+                                </p>
+                                    
+                                <p>This issue was discovered by Alvaro Munoz and Alexander Mirosh of the HP
        Enterprise Security Team and reported to the Apache Tomcat Security Team
        on 5 July 2016. It was made public on 27 October 2016.</p>
-
-    
-<p>Affects: 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36</p>
-
-    
-<p>
-<strong>Low: Timing Attack</strong>

[... 1323 lines stripped ...]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message