You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by kk...@apache.org on 2020/02/13 15:24:18 UTC
svn commit: r1873980 [27/34] - /tomcat/site/trunk/docs/
Modified: tomcat/site/trunk/docs/security-7.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-7.html?rev=1873980&r1=1873979&r2=1873980&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-7.html (original)
+++ tomcat/site/trunk/docs/security-7.html Thu Feb 13 15:24:17 2020
@@ -1,371 +1,10 @@
<!DOCTYPE html SYSTEM "about:legacy-compat">
-<html lang="en">
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<link href="res/css/tomcat.css" rel="stylesheet" type="text/css">
-<link href="res/css/fonts/fonts.css" rel="stylesheet" type="text/css">
-<title>Apache Tomcat® - Apache Tomcat 7 vulnerabilities</title>
-<meta name="author" content="Apache Tomcat Project">
-</head>
-<body>
-<div id="wrapper">
-<header id="header">
-<div class="clearfix">
-<div class="menu-toggler pull-left" tabindex="1">
-<div class="hamburger"></div>
-</div>
-<a href="http://tomcat.apache.org/"><img class="tomcat-logo pull-left noPrint" alt="Tomcat Home" src="res/images/tomcat.png"></a>
-<h1 class="pull-left">Apache Tomcat<sup>®</sup>
-</h1>
-<div class="asf-logos pull-right">
-<a href="https://www.apache.org/foundation/contributing.html" target="_blank" class="pull-left"><img src="https://www.apache.org/images/SupportApache-small.png" class="support-asf" alt="Support Apache"></a><a href="http://www.apache.org/" target="_blank" class="pull-left"><img src="res/images/asf_logo.svg" class="asf-logo" alt="The Apache Software Foundation"></a>
-</div>
-</div>
-</header>
-<main id="middle">
-<div>
-<div id="mainLeft">
-<div id="nav-wrapper">
-<form action="https://www.google.com/search" method="get">
-<div class="searchbox">
-<input value="tomcat.apache.org" name="sitesearch" type="hidden"><input aria-label="Search text" placeholder="Search…" required="required" name="q" id="query" type="search"><button>GO</button>
-</div>
-</form>
-<div class="asfevents">
-<a href="https://www.apache.org/events/current-event.html"><img src="https://www.apache.org/events/current-event-234x60.png" alt="Next ASF event"><br>
+<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1"><link href="res/css/tomcat.css" rel="stylesheet" type="text/css"><link href="res/css/fonts/fonts.css" rel="stylesheet" type="text/css"><title>Apache Tomcat® - Apache Tomcat 7 vulnerabilities</title><meta name="author" content="Apache Tomcat Project"></head><body><div id="wrapper"><header id="header"><div class="clearfix"><div class="menu-toggler pull-left" tabindex="1"><div class="hamburger"></div></div><a href="http://tomcat.apache.org/"><img class="tomcat-logo pull-left noPrint" alt="Tomcat Home" src="res/images/tomcat.png"></a><h1 class="pull-left">Apache Tomcat<sup>®</sup></h1><div class="asf-logos pull-right"><a href="https://www.apache.org/foundation/contributing.html" target="_blank" class="pull-left"><img src="https://www.apache.org/images/SupportApache-small.png" class="support-asf" alt="Support Apache"></a><a h
ref="http://www.apache.org/" target="_blank" class="pull-left"><img src="res/images/asf_logo.svg" class="asf-logo" alt="The Apache Software Foundation"></a></div></div></header><main id="middle"><div><div id="mainLeft"><div id="nav-wrapper"><form action="https://www.google.com/search" method="get"><div class="searchbox"><input value="tomcat.apache.org" name="sitesearch" type="hidden"><input aria-label="Search text" placeholder="Search…" required="required" name="q" id="query" type="search"><button>GO</button></div></form><div class="asfevents"><a href="https://www.apache.org/events/current-event.html"><img src="https://www.apache.org/events/current-event-234x60.png" alt="Next ASF event"><br>
Save the date!
- </a>
-</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>Download</h2>
-<ul>
-<li>
-<a href="./whichversion.html">Which version?</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-90.cgi">Tomcat 9</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-80.cgi">Tomcat 8</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-70.cgi">Tomcat 7</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-connectors.cgi">Tomcat Connectors</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-native.cgi">Tomcat Native</a>
-</li>
-<li>
-<a href="https://tomcat.apache.org/download-taglibs.cgi">Taglibs</a>
-</li>
-<li>
-<a href="https://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-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="https://cwiki.apache.org/confluence/display/TOMCAT">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="https://cwiki.apache.org/confluence/display/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="./source.html">Source code</a>
-</li>
-<li>
-<a href="./ci.html">Buildbot</a>
-</li>
-<li>
-<a href="https://cwiki.apache.org/confluence/x/vIPzBQ">Translations</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="https://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="https://www.redbubble.com/people/comdev/works/30885254-apache-tomcat">Swag</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="https://www.apache.org/foundation/contributing.html">Support Apache</a>
-</li>
-<li>
-<a href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
-</li>
-<li>
-<a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
-</li>
-<li>
-<a href="http://www.apache.org/licenses/">License</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_7.x_vulnerabilities">Apache Tomcat 7.x vulnerabilities</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.99">Fixed in Apache Tomcat 7.0.99</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.94">Fixed in Apache Tomcat 7.0.94</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.91">Fixed in Apache Tomcat 7.0.91</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.90">Fixed in Apache Tomcat 7.0.90</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.89">Fixed in Apache Tomcat 7.0.89</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.88">Fixed in Apache Tomcat 7.0.88</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.85">Fixed in Apache Tomcat 7.0.85</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.84">Fixed in Apache Tomcat 7.0.84</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.82">Fixed in Apache Tomcat 7.0.82</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.81">Fixed in Apache Tomcat 7.0.81</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.79">Fixed in Apache Tomcat 7.0.79</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.78">Fixed in Apache Tomcat 7.0.78</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.77">Fixed in Apache Tomcat 7.0.77</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.76">Fixed in Apache Tomcat 7.0.76</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.75">Fixed in Apache Tomcat 7.0.75</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.73">Fixed in Apache Tomcat 7.0.73</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.72">Fixed in Apache Tomcat 7.0.72</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.70">Fixed in Apache Tomcat 7.0.70</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.68">Fixed in Apache Tomcat 7.0.68</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.67">Fixed in Apache Tomcat 7.0.67</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.65">Fixed in Apache Tomcat 7.0.65</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.59">Fixed in Apache Tomcat 7.0.59</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.55">Fixed in Apache Tomcat 7.0.55</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.54">Fixed in Apache Tomcat 7.0.54</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.53">Fixed in Apache Tomcat 7.0.53</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.52">Fixed in Apache Tomcat 7.0.52</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.50">Fixed in Apache Tomcat 7.0.50</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.47">Fixed in Apache Tomcat 7.0.47</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.40">Fixed in Apache Tomcat 7.0.40</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.33">Fixed in Apache Tomcat 7.0.33</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.32">Fixed in Apache Tomcat 7.0.32</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.30">Fixed in Apache Tomcat 7.0.30</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.28">Fixed in Apache Tomcat 7.0.28</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.23">Fixed in Apache Tomcat 7.0.23</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.22">Fixed in Apache Tomcat 7.0.22</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.21">Fixed in Apache Tomcat 7.0.21</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.20">Fixed in Apache Tomcat 7.0.20</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.19">Fixed in Apache Tomcat 7.0.19</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.14">Fixed in Apache Tomcat 7.0.14</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.12">Fixed in Apache Tomcat 7.0.12</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.11">Fixed in Apache Tomcat 7.0.11</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.8">Fixed in Apache Tomcat 7.0.8</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.6">Fixed in Apache Tomcat 7.0.6</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.5">Fixed in Apache Tomcat 7.0.5</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.4">Fixed in Apache Tomcat 7.0.4</a>
-</li>
-<li>
-<a href="#Fixed_in_Apache_Tomcat_7.0.2">Fixed in Apache Tomcat 7.0.2</a>
-</li>
-<li>
-<a href="#Not_a_vulnerability_in_Tomcat">Not a vulnerability in Tomcat</a>
-</li>
-</ul>
-
-</div>
-<h3 id="Apache_Tomcat_7.x_vulnerabilities">Apache Tomcat 7.x vulnerabilities</h3>
-<div class="text">
-
-<p>This page lists all security vulnerabilities fixed in released versions
+ </a></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>Download</h2><ul><li><a href="./whichversion.html">Which version?</a></li><li><a href="https://tomcat.apache.org/download-90.cgi">Tomcat 9</a></li><li><a href="https://tomcat.apache.org/download-80.cgi">Tomcat 8</a></li><li><a href="https://tomcat.apache.org/download-70.cgi">Tomcat 7</a></li><li><a href="https://tomcat.apache.org/download-connectors.cgi">Tomcat Connectors</a></li><li><a href="https://tomcat.apache.org/download-native.cgi">Tomcat Native</a></li><li><a href="https://tomcat.apache.org/download-taglibs.cgi">Taglibs</a></li><li><a href="https://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><l
i><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="https://cwiki.apache.org/confluence/display/TOMCAT">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="https://cwiki.apache.org/confluence/display/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="./source.html">Source code</a></li><li><a href="./ci.html">Buildbot</a></li><li><a href="https://cwiki.apache.org/confluence/x/vIPzBQ">Translations</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="https://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="https://www.redbubble.com/people/comdev/works/30885254-apache-tomcat">Swag</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="https://www.apache.org/foundation/contributing.html">Support Apache</a></li><li><a href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li><li><a href="http://www.apache.org/licenses/">License</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_7.x_vulnerabilities">Apache Tomcat 7.x vulnerabilities</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.99">Fixed in Apache Tomcat 7.0.99</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.94">Fixed in Apache Tomcat 7.0.94</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.91">Fixed in Apache Tomcat 7.0.91</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.90">Fixed in Apache Tomcat 7.0.90</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.89">Fixed in Apache Tomcat 7.0.89</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.88">Fixed in Apache Tomcat 7.0.88</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.85">Fixed in Apache Tomcat 7.0.85</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.84">Fixed in Apache Tomcat 7.0.84</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.82">Fixed in Apache Tomcat 7.0.82</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.81">Fixed in Apache Tomcat 7.0.81</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.79">Fixed in Apache Tomcat 7.0.
79</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.78">Fixed in Apache Tomcat 7.0.78</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.77">Fixed in Apache Tomcat 7.0.77</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.76">Fixed in Apache Tomcat 7.0.76</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.75">Fixed in Apache Tomcat 7.0.75</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.73">Fixed in Apache Tomcat 7.0.73</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.72">Fixed in Apache Tomcat 7.0.72</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.70">Fixed in Apache Tomcat 7.0.70</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.68">Fixed in Apache Tomcat 7.0.68</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.67">Fixed in Apache Tomcat 7.0.67</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.65">Fixed in Apache Tomcat 7.0.65</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.59">Fixed in Apache Tomcat 7.0.59</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.55">Fixed in Apache Tomcat 7.0.5
5</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.54">Fixed in Apache Tomcat 7.0.54</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.53">Fixed in Apache Tomcat 7.0.53</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.52">Fixed in Apache Tomcat 7.0.52</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.50">Fixed in Apache Tomcat 7.0.50</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.47">Fixed in Apache Tomcat 7.0.47</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.40">Fixed in Apache Tomcat 7.0.40</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.33">Fixed in Apache Tomcat 7.0.33</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.32">Fixed in Apache Tomcat 7.0.32</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.30">Fixed in Apache Tomcat 7.0.30</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.28">Fixed in Apache Tomcat 7.0.28</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.23">Fixed in Apache Tomcat 7.0.23</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.22">Fixed in Apache Tomcat 7.0.22
</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.21">Fixed in Apache Tomcat 7.0.21</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.20">Fixed in Apache Tomcat 7.0.20</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.19">Fixed in Apache Tomcat 7.0.19</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.14">Fixed in Apache Tomcat 7.0.14</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.12">Fixed in Apache Tomcat 7.0.12</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.11">Fixed in Apache Tomcat 7.0.11</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.8">Fixed in Apache Tomcat 7.0.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.6">Fixed in Apache Tomcat 7.0.6</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.5">Fixed in Apache Tomcat 7.0.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.4">Fixed in Apache Tomcat 7.0.4</a></li><li><a href="#Fixed_in_Apache_Tomcat_7.0.2">Fixed in Apache Tomcat 7.0.2</a></li><li><a href="#Not_a_vulnerability_in_Tomcat">Not a vulnerability in Tomcat</a></li></
ul>
+</div><h3 id="Apache_Tomcat_7.x_vulnerabilities">Apache Tomcat 7.x vulnerabilities</h3><div class="text">
+ <p>This page lists all security vulnerabilities fixed in released versions
of Apache Tomcat 7.x. Each vulnerability is given a
<a href="security-impact.html">security impact rating</a> by the Apache
Tomcat security team — please note that this rating may vary from
@@ -373,14 +12,11 @@
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
+ <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
+ <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 7.0 those are
<a href="/tomcat-7.0-doc/building.html"><code>building.html</code></a> and
@@ -390,109 +26,75 @@
<a href="/tomcat-7.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
+ <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>
-
-<p>If you have encountered an unlisted security vulnerability or other
+ <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_7.0.99">
-<span class="pull-right">17 December 2019</span> Fixed in Apache Tomcat 7.0.99</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.99"><span class="pull-right">17 December 2019</span> Fixed in Apache Tomcat 7.0.99</h3><div class="text">
-
-<p>
-<strong>Low: Session fixation</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563" rel="nofollow">CVE-2019-17563</a>
-</p>
+ <p><strong>Low: Session fixation</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563" rel="nofollow">CVE-2019-17563</a></p>
-
-<p>When using FORM authentication there was a narrow window where an
+ <p>When using FORM authentication there was a narrow window where an
attacker could perform a session fixation attack. The window was
considered too narrow for an exploit to be practical but, erring on the
side of caution, this issue has been treated as a security
vulnerability.</p>
-
-<p>This was fixed with commit
+ <p>This was fixed with commit
<a href="https://github.com/apache/tomcat/commit/ab72a10">ab72a10</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team by William
+ <p>This issue was reported to the Apache Tomcat Security Team by William
Marlow (IBM) on 19 November 2019. The issue was made public on 18
December 2019.</p>
-
-<p>Affects: 7.0.0 to 7.0.98</p>
+ <p>Affects: 7.0.0 to 7.0.98</p>
-
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.98 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.98 but the
release vote for the 7.0.98 release candidate did not pass. Therefore,
although users must download 7.0.99 to obtain a version that includes
the fix for this issue, version78.0.98 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>
-<strong>Moderate: Local Privilege Escalation</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418" rel="nofollow">CVE-2019-12418</a>
-</p>
+ <p><strong>Moderate: Local Privilege Escalation</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418" rel="nofollow">CVE-2019-12418</a></p>
-
-<p>When Tomcat is configured with the JMX Remote Lifecycle Listener, a local
+ <p>When Tomcat is configured with the JMX Remote Lifecycle Listener, a local
attacker without access to the Tomcat process or configuration files is
able to manipulate the RMI registry to perform a man-in-the-middle attack
to capture user names and passwords used to access the JMX interface. The
attacker can then use these credentials to access the JMX interface and
gain complete control over the Tomcat instance.</p>
-
-<p>The JMX Remote Lifecycle Listener will be deprecated in future Tomcat
+ <p>The JMX Remote Lifecycle Listener will be deprecated in future Tomcat
releases, will be removed for Tomcat 10 and may be removed from all
Tomcat releases some time after 31 December 2020.</p>
-
-<p>Users should also be aware of <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2684" rel="nofollow">CVE-2019-2684</a>, a JRE
+ <p>Users should also be aware of <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2684" rel="nofollow">CVE-2019-2684</a>, a JRE
vulnerability that enables this issue to be exploited remotely.</p>
-
-<p>This was fixed with commit
+ <p>This was fixed with commit
<a href="https://github.com/apache/tomcat/commit/bef3f40">bef3f40</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team by An Trinh of
+ <p>This issue was reported to the Apache Tomcat Security Team by An Trinh of
Viettel Cyber Security on 10 October 2019. The issue was made public on 18
December 2019.</p>
-
-<p>Affects: 7.0.0 to 7.0.97</p>
+ <p>Affects: 7.0.0 to 7.0.97</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.94">
-<span class="pull-right">12 April 2019</span> Fixed in Apache Tomcat 7.0.94</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.94"><span class="pull-right">12 April 2019</span> Fixed in Apache Tomcat 7.0.94</h3><div class="text">
-
-<p>
-<strong>Important: Remote Code Execution on Windows</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232" rel="nofollow">CVE-2019-0232</a>
-</p>
+ <p><strong>Important: Remote Code Execution on Windows</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232" rel="nofollow">CVE-2019-0232</a></p>
-
-<p>When running on Windows with enableCmdLineArguments enabled, the CGI
+ <p>When running on Windows with enableCmdLineArguments enabled, the CGI
Servlet is vulnerable to Remote Code Execution due to a bug in the way
the JRE passes command line arguments to Windows. The CGI Servlet is
disabled by default. For a detailed explanation of the JRE behaviour, see
@@ -501,230 +103,148 @@
<a href="https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/">MSDN
blog</a>.</p>
-
-<p>This was fixed with commit
+ <p>This was fixed with commit
<a href="https://github.com/apache/tomcat/commit/7f0221b">7f0221b</a>.</p>
-
-<p>This issue was identified by Nightwatch Cybersecurity Research and
+ <p>This issue was identified by Nightwatch Cybersecurity Research and
reported to the Apache Tomcat security team via the bug bounty program
sponsored by the EU FOSSA-2 project on 3rd March 2019. The issue was made
public on 10 April 2019.</p>
-
-<p>Affects: 7.0.0 to 7.0.93</p>
+ <p>Affects: 7.0.0 to 7.0.93</p>
-
-<p>
-<strong>Low: XSS in SSI printenv</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221" rel="nofollow">CVE-2019-0221</a>
-</p>
+ <p><strong>Low: XSS in SSI printenv</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221" rel="nofollow">CVE-2019-0221</a></p>
-
-<p>The SSI printenv command echoes user provided data without escaping and
+ <p>The SSI printenv command echoes user provided data without escaping and
is, therefore, vulnerable to XSS. SSI is disabled by default. The
printenv command is intended for debugging and is unlikely to be present
in a production website.</p>
-
-<p>This was fixed with commit
+ <p>This was fixed with commit
<a href="https://github.com/apache/tomcat/commit/44ec74c">44ec74c</a>.</p>
-
-<p>This issue was identified by Nightwatch Cybersecurity Research and
+ <p>This issue was identified by Nightwatch Cybersecurity Research and
reported to the Apache Tomcat security team via the bug bounty program
sponsored by the EU FOSSA-2 project on 7th March 2019. The issue was made
public on 17 May 2019.</p>
-
-<p>Affects: 7.0.0 to 7.0.93</p>
+ <p>Affects: 7.0.0 to 7.0.93</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.91"><span class="pull-right">19 September 2018</span> Fixed in Apache Tomcat 7.0.91</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.91">
-<span class="pull-right">19 September 2018</span> Fixed in Apache Tomcat 7.0.91</h3>
-<div class="text">
-
-
-<p>
-<strong>Moderate: Open Redirect</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11784" rel="nofollow">CVE-2018-11784</a>
-</p>
+ <p><strong>Moderate: Open Redirect</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11784" rel="nofollow">CVE-2018-11784</a></p>
-
-<p>When the default servlet returned a redirect to a directory (e.g.
+ <p>When the default servlet returned a redirect to a directory (e.g.
redirecting to <code>/foo/</code> when the user requested
<code>/foo</code>) a specially crafted URL could be used to cause the
redirect to be generated to any URI of the attackers choice.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1840057">1840057</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1840057">1840057</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team by Sergey
+ <p>This issue was reported to the Apache Tomcat Security Team by Sergey
Bobrov on 28 August 2018 and made public on 3 October 2018.</p>
-
-<p>Affects: 7.0.23 to 7.0.90</p>
+ <p>Affects: 7.0.23 to 7.0.90</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.90">
-<span class="pull-right">7 July 2018</span> Fixed in Apache Tomcat 7.0.90</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.90"><span class="pull-right">7 July 2018</span> Fixed in Apache Tomcat 7.0.90</h3><div class="text">
-
-<p>
-<strong>Low: host name verification missing in WebSocket client</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8034" rel="nofollow">CVE-2018-8034</a>
-</p>
+ <p><strong>Low: host name verification missing in WebSocket client</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8034" rel="nofollow">CVE-2018-8034</a></p>
-
-<p>The host name verification when using TLS with the WebSocket client was
+ <p>The host name verification when using TLS with the WebSocket client was
missing. It is now enabled by default.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1833760">1833760</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1833760">1833760</a>.</p>
-
-<p>This issue was reported publicly on 11 June 2018 and formally announced as
+ <p>This issue was reported publicly on 11 June 2018 and formally announced as
a vulnerability on 22 July 2018.</p>
-
-<p>Affects: 7.0.25 to 7.0.88</p>
+ <p>Affects: 7.0.25 to 7.0.88</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.89"><span class="pull-right">not released</span> Fixed in Apache Tomcat 7.0.89</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.89">
-<span class="pull-right">not released</span> Fixed in Apache Tomcat 7.0.89</h3>
-<div class="text">
-
-
-<p>
-<strong>Low: CORS filter has insecure defaults</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8014" rel="nofollow">CVE-2018-8014</a>
-</p>
+ <p><strong>Low: CORS filter has insecure defaults</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8014" rel="nofollow">CVE-2018-8014</a></p>
-
-<p>The defaults settings for the CORS filter are insecure and enable
+ <p>The defaults settings for the CORS filter are insecure and enable
<code>supportsCredentials</code> for all origins. It is expected that
users of the CORS filter will have configured it appropriately for their
environment rather than using it in the default configuration. Therefore,
it is expected that most users will not be impacted by this issue.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1831730">1831730</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1831730">1831730</a>.</p>
-
-<p>This issue was reported publicly on 1 May 2018 and formally announced as
+ <p>This issue was reported publicly on 1 May 2018 and formally announced as
a vulnerability on 16 May 2018.</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.88">
-<span class="pull-right">16 May 2018</span> Fixed in Apache Tomcat 7.0.88</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.88"><span class="pull-right">16 May 2018</span> Fixed in Apache Tomcat 7.0.88</h3><div class="text">
-
-<p>
-<strong>Important: A bug in the UTF-8 decoder can lead to DoS</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1336" rel="nofollow">CVE-2018-1336</a>
-</p>
+ <p><strong>Important: A bug in the UTF-8 decoder can lead to DoS</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1336" rel="nofollow">CVE-2018-1336</a></p>
-
-<p>An improper handing of overflow in the UTF-8 decoder with
+ <p>An improper handing of overflow in the UTF-8 decoder with
supplementary characters can lead to an infinite loop in the
decoder causing a Denial of Service.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1830376">1830376</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1830376">1830376</a>.</p>
-
-<p>This issue was reported publicly on 6 April 2018 and formally announced as
+ <p>This issue was reported publicly on 6 April 2018 and formally announced as
a vulnerability on 22 July 2018.</p>
-
-<p>Affects: 7.0.28 to 7.0.88</p>
+ <p>Affects: 7.0.28 to 7.0.88</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.85"><span class="pull-right">13 February 2018</span> Fixed in Apache Tomcat 7.0.85</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.85">
-<span class="pull-right">13 February 2018</span> Fixed in Apache Tomcat 7.0.85</h3>
-<div class="text">
-
-
-<p>
-<strong>Important: Security constraint annotations applied too
- late</strong> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1305" rel="nofollow">CVE-2018-1305</a>
-</p>
+ <p><strong>Important: Security constraint annotations applied too
+ late</strong> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1305" rel="nofollow">CVE-2018-1305</a></p>
-
-<p>Security constraints defined by annotations of Servlets were only applied
+ <p>Security constraints defined by annotations of Servlets were only applied
once a Servlet had been loaded. Because security constraints defined in
this way apply to the URL pattern and any URLs below that point, it was
possible - depending on the order Servlets were loaded - for some
security constraints not to be applied. This could have exposed resources
to users who were not authorised to access them.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1823322">1823322</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1823322">1823322</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1824360">1824360</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security on 1 February
+ <p>This issue was identified by the Apache Tomcat Security on 1 February
2018 and made public on 23 February 2018.</p>
-
-<p>Affects: 7.0.0 to 7.0.84</p>
+ <p>Affects: 7.0.0 to 7.0.84</p>
-
-<p>
-<strong>Important: Security constraints mapped to context root are
- ignored</strong> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1304" rel="nofollow">CVE-2018-1304</a>
-</p>
+ <p><strong>Important: Security constraints mapped to context root are
+ ignored</strong> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1304" rel="nofollow">CVE-2018-1304</a></p>
-
-<p>The URL pattern of "" (the empty string) which exactly maps to the
+ <p>The URL pattern of "" (the empty string) which exactly maps to the
context root was not correctly handled when used as part of a security
constraint definition. This caused the constraint to be ignored. It was,
therefore, possible for unauthorised users to gain access to web
application resources that should have been protected. Only security
constraints with a URL pattern of the empty string were affected.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1823309">1823309</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1823309">1823309</a>.</p>
-
-<p>This issue was reported publicly as <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=62067">62067</a> on 31 January 2018
+ <p>This issue was reported publicly as <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=62067">62067</a> on 31 January 2018
and the security implications identified by the Apache Tomcat Security
Team the same day. It was made public on 23 February 2018.</p>
-
-<p>Affects: 7.0.0 to 7.0.84</p>
+ <p>Affects: 7.0.0 to 7.0.84</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.84">
-<span class="pull-right">24 January 2018</span> Fixed in Apache Tomcat 7.0.84</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.84"><span class="pull-right">24 January 2018</span> Fixed in Apache Tomcat 7.0.84</h3><div class="text">
-
-<p>
-<strong>Low: Incorrectly documented CGI search algorithm</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15706" rel="nofollow">CVE-2017-15706</a>
-</p>
+ <p><strong>Low: Incorrectly documented CGI search algorithm</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15706" rel="nofollow">CVE-2017-15706</a></p>
-
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.83 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.83 but the
release vote for the 7.0.83 release candidate did not pass. Therefore,
although users must download 7.0.84 to obtain a version that includes
the fix for this issue, version 7.0.83 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>As part of the fix for bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61201">61201</a>, the description of the
+ <p>As part of the fix for bug <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61201">61201</a>, the description of the
search algorithm used by the CGI Servlet to identify which script to
execute was updated. The update was not correct. As a result, some
scripts may have failed to execute as expected and other scripts may have
@@ -732,308 +252,201 @@
has remained unchanged in this regard. It is only the documentation of
the behaviour that was wrong and has been corrected.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1814828">1814828</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1814828">1814828</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team by Jan Michael
+ <p>This issue was reported to the Apache Tomcat Security Team by Jan Michael
Greiner on 17 September 2017 and made public on 31 January 2018.</p>
-
-<p>Affects: 7.0.79 to 7.0.82</p>
+ <p>Affects: 7.0.79 to 7.0.82</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.82">
-<span class="pull-right">4 October 2017</span> Fixed in Apache Tomcat 7.0.82</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.82"><span class="pull-right">4 October 2017</span> Fixed in Apache Tomcat 7.0.82</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><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 with HTTP PUTs enabled (e.g. via setting the
+ <p>When running with HTTP PUTs enabled (e.g. via setting the
<code>readonly</code> initialisation parameter of the Default servlet 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="https://svn.apache.org/viewvc?view=rev&rev=1809978">1809978</a>,
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1809978">1809978</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1809992">1809992</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1810014">1810014</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1810026">1810026</a>.</p>
-
-<p>This issue was first reported publicly followed by multiple reports to
+ <p>This issue was first reported publicly followed by multiple reports to
the Apache Tomcat Security Team on 20 September 2017.</p>
-
-<p>Affects: 7.0.0 to 7.0.81</p>
+ <p>Affects: 7.0.0 to 7.0.81</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.81">
-<span class="pull-right">16 August 2017</span> Fixed in Apache Tomcat 7.0.81</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.81"><span class="pull-right">16 August 2017</span> Fixed in Apache Tomcat 7.0.81</h3><div class="text">
-
-<p>
-<strong>Important: Information Disclosure</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12616" rel="nofollow">CVE-2017-12616</a>
-</p>
+ <p><strong>Important: Information Disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12616" rel="nofollow">CVE-2017-12616</a></p>
-
-<p>When using a VirtualDirContext it was possible to bypass security
+ <p>When using a VirtualDirContext it was possible to bypass security
constraints and/or view the source code of JSPs for resources served by
the VirtualDirContext using a specially crafted request.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1804729">1804729</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1804729">1804729</a>.</p>
-
-<p>This issue was identified by the Tomcat Security Team on 10 August 2017
+ <p>This issue was identified by the Tomcat Security Team on 10 August 2017
and made public on 19 September 2017.</p>
-
-<p>Affects: 7.0.0 to 7.0.80</p>
+ <p>Affects: 7.0.0 to 7.0.80</p>
-
-<p>
-<strong>Important: Remote Code Execution</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615" rel="nofollow">CVE-2017-12615</a>
-</p>
+ <p><strong>Important: Remote Code Execution</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615" rel="nofollow">CVE-2017-12615</a></p>
-
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.80 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.80 but the
release vote for the 7.0.81 release candidate did not pass. Therefore,
although users must download 7.0.81 to obtain a version that includes
the fix for this issue, version 7.0.80 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>When running on Windows with HTTP PUTs enabled (e.g. via setting the
+ <p>When running on Windows 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="https://svn.apache.org/viewvc?view=rev&rev=1804604">1804604</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1804604">1804604</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1804729">1804729</a>.</p>
-
-<p>This issue was reported responsibly to the Apache Tomcat Security Team by
+ <p>This issue was reported responsibly to the Apache Tomcat Security Team by
iswin from 360-sg-lab (360è§æå®éªå®¤) on 26 July 2017 and made public on 19
September 2017.</p>
-
-<p>Affects: 7.0.0 to 7.0.79</p>
+ <p>Affects: 7.0.0 to 7.0.79</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.79">
-<span class="pull-right">1 July 2017</span> Fixed in Apache Tomcat 7.0.79</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.79"><span class="pull-right">1 July 2017</span> Fixed in Apache Tomcat 7.0.79</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1795816">1795816</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1795816">1795816</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>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: 7.0.41 to 7.0.78</p>
+ <p>Affects: 7.0.41 to 7.0.78</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.78"><span class="pull-right">16 May 2017</span> Fixed in Apache Tomcat 7.0.78</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.78">
-<span class="pull-right">16 May 2017</span> Fixed in Apache Tomcat 7.0.78</h3>
-<div class="text">
-
-
-<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><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>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>
+ </ul>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1793471">1793471</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1793471">1793471</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1793491">1793491</a>.</p>
-
-<p>This issue was reported responsibly to the Apache Tomcat Security Team by
+ <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: 7.0.0 to 7.0.77</p>
+ <p>Affects: 7.0.0 to 7.0.77</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.77">
-<span class="pull-right">2 April 2017</span> Fixed in Apache Tomcat 7.0.77</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.77"><span class="pull-right">2 April 2017</span> Fixed in Apache Tomcat 7.0.77</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1789008">1789008</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1789008">1789008</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+ <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: 7.0.0 to 7.0.76</p>
+ <p>Affects: 7.0.0 to 7.0.76</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.76">
-<span class="pull-right">16 March 2017</span> Fixed in Apache Tomcat 7.0.76</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.76"><span class="pull-right">16 March 2017</span> Fixed in Apache Tomcat 7.0.76</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1785777">1785777</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1785777">1785777</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 20
+ <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: 7.0.0 to 7.0.75</p>
+ <p>Affects: 7.0.0 to 7.0.75</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.75">
-<span class="pull-right">24 January 2017</span> Fixed in Apache Tomcat 7.0.75</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.75"><span class="pull-right">24 January 2017</span> Fixed in Apache Tomcat 7.0.75</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><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>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.74 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.74 but the
release vote for the 7.0.74 release candidate did not pass. Therefore,
although users must download 7.0.75 to obtain a version that includes
the fix for this issue, version 7.0.74 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>A bug in the error handling of the send file code for the NIO HTTP
+ <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="https://svn.apache.org/viewvc?view=rev&rev=1777471">1777471</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1777471">1777471</a>.</p>
-
-<p>This issue was identified as affecting 7.0.x by the Apache Tomcat Security
+ <p>This issue was identified as affecting 7.0.x by the Apache Tomcat Security
Team on 3 January 2016 and made public on 5 January 2017.</p>
-
-<p>Affects: 7.0.0 to 7.0.73</p>
+ <p>Affects: 7.0.0 to 7.0.73</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.73">
-<span class="pull-right">14 November 2016</span> Fixed in Apache Tomcat 7.0.73</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.73"><span class="pull-right">14 November 2016</span> Fixed in Apache Tomcat 7.0.73</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><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>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
@@ -1041,183 +454,123 @@
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="https://svn.apache.org/viewvc?view=rev&rev=1767676">1767676</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1767676">1767676</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team on 19 October
+ <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: 7.0.0 to 7.0.72</p>
+ <p>Affects: 7.0.0 to 7.0.72</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1767675">1767675</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1767675">1767675</a>.</p>
-
-<p>This issue was reported to the Apache Tomcat Security Team on 11
+ <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: 7.0.0 to 7.0.72</p>
+ <p>Affects: 7.0.0 to 7.0.72</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.72"><span class="pull-right">19 September 2016</span> Fixed in Apache Tomcat 7.0.72</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.72">
-<span class="pull-right">19 September 2016</span> Fixed in Apache Tomcat 7.0.72</h3>
-<div class="text">
-
-
-<p>
-<i>Note: The issues below were fixed in Apache Tomcat 7.0.71 but the
+ <p><i>Note: The issues below were fixed in Apache Tomcat 7.0.71 but the
release vote for the 7.0.71 release candidate did not pass. Therefore,
although users must download 7.0.72 to obtain a version that includes
fixes for these issues, version 7.0.71 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1757275">1757275</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1757275">1757275</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 18
+ <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: 7.0.0 to 7.0.70</p>
+ <p>Affects: 7.0.0 to 7.0.70</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1758495">1758495</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1758495">1758495</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1763236">1763236</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 27
+ <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: 7.0.0 to 7.0.70</p>
+ <p>Affects: 7.0.0 to 7.0.70</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1754728">1754728</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1754728">1754728</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 27
+ <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: 7.0.0 to 7.0.70</p>
+ <p>Affects: 7.0.0 to 7.0.70</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><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>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="https://svn.apache.org/viewvc?view=rev&rev=1754902">1754902</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1754902">1754902</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1760309">1760309</a>.</p>
-
-<p>This issue was discovered by Alvaro Munoz and Alexander Mirosh of the HP
+ <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: 7.0.0 to 7.0.70</p>
+ <p>Affects: 7.0.0 to 7.0.70</p>
-
-<p>
-<strong>Low: Timing Attack</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762" rel="nofollow">CVE-2016-0762</a>
-</p>
+ <p><strong>Low: Timing Attack</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762" rel="nofollow">CVE-2016-0762</a></p>
-
-<p>The Realm implementations did not process the supplied password if the
+ <p>The Realm implementations did not process the supplied password if the
supplied user name did not exist. This made a timing attack possible to
determine valid user names. Note that the default configuration includes
the LockOutRealm which makes exploitation of this vulnerability
harder.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1758502">1758502</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1758502">1758502</a>.</p>
-
-<p>This issue was identified by the Apache Tomcat Security Team on 1 January
+ <p>This issue was identified by the Apache Tomcat Security Team on 1 January
2016 and made public on 27 October 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.70</p>
+ <p>Affects: 7.0.0 to 7.0.70</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.70"><span class="pull-right">20 June 2016</span> Fixed in Apache Tomcat 7.0.70</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.70">
-<span class="pull-right">20 June 2016</span> Fixed in Apache Tomcat 7.0.70</h3>
-<div class="text">
-
-
-<p>
-<strong>Moderate: Denial of Service</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092" rel="nofollow">CVE-2016-3092</a>
-</p>
+ <p><strong>Moderate: Denial of Service</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092" rel="nofollow">CVE-2016-3092</a></p>
-
-<p>Apache Tomcat uses a package renamed copy of Apache Commons FileUpload to
+ <p>Apache Tomcat uses a package renamed copy of Apache Commons FileUpload to
implement the file upload requirements of the Servlet specification. A
denial of service vulnerability was identified in Commons FileUpload that
occurred when the length of the multipart boundary was just below the
@@ -1225,31 +578,20 @@
caused the file upload process to take several orders of magnitude
longer than if the boundary was the typical tens of bytes long.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1743742">1743742</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1743742">1743742</a>.</p>
-
-<p>This issue was identified by the TERASOLUNA Framework Development Team
+ <p>This issue was identified by the TERASOLUNA Framework Development Team
and reported to the Apache Commons team via JPCERT on 9 May 2016. It was
made public on 21 June 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.69</p>
+ <p>Affects: 7.0.0 to 7.0.69</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.68">
-<span class="pull-right">16 February 2016</span> Fixed in Apache Tomcat 7.0.68</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.68"><span class="pull-right">16 February 2016</span> Fixed in Apache Tomcat 7.0.68</h3><div class="text">
-
-<p>
-<strong>Low: Directory disclosure</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5345" rel="nofollow">CVE-2015-5345</a>
-</p>
+ <p><strong>Low: Directory disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5345" rel="nofollow">CVE-2015-5345</a></p>
-
-<p>When accessing a directory protected by a security constraint with a URL
+ <p>When accessing a directory protected by a security constraint with a URL
that did not end in a slash, Tomcat would redirect to the URL with the
trailing slash thereby confirming the presence of the directory before
processing the security constraint. It was therefore possible for a user
@@ -1258,8 +600,7 @@
web application in which case the presence of the web application was
confirmed, even if a user did not have access.</p>
-
-<p>The solution was to implement the redirect in the DefaultServlet so that
+ <p>The solution was to implement the redirect in the DefaultServlet so that
any security constraints and/or security enforcing Filters were processed
before the redirect. The Tomcat team recognised that moving the redirect
could cause regressions so two new Context configuration options
@@ -1273,26 +614,19 @@
more serious than the security risk associated with being able to
determine if a web application was deployed at a given path.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1715213">1715213</a>,
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1715213">1715213</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1716860">1716860</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1717212">1717212</a>.</p>
-
-<p>This issue was identified by Mark Koek of QCSec on 12 October 2015 and
+ <p>This issue was identified by Mark Koek of QCSec on 12 October 2015 and
made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.67</p>
+ <p>Affects: 7.0.0 to 7.0.67</p>
-
-<p>
-<strong>Moderate: CSRF token leak</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5351" rel="nofollow">CVE-2015-5351</a>
-</p>
+ <p><strong>Moderate: CSRF token leak</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5351" rel="nofollow">CVE-2015-5351</a></p>
-
-<p>The index page of the Manager and Host Manager applications included a
+ <p>The index page of the Manager and Host Manager applications included a
valid CSRF token when issuing a redirect as a result of an
unauthenticated request to the root of the web application. If an
attacker had access to the Manager or Host Manager applications
@@ -1300,29 +634,21 @@
exposed to the Internet), this token could then be used by the attacker
to construct a CSRF attack.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1720661">1720661</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1720661">1720661</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1720663">1720663</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 8 December 2015
+ <p>This issue was identified by the Tomcat security team on 8 December 2015
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.1 to 7.0.67</p>
+ <p>Affects: 7.0.1 to 7.0.67</p>
-
-<p>
-<strong>Low: Security Manager bypass</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0706" rel="nofollow">CVE-2016-0706</a>
-</p>
+ <p><strong>Low: Security Manager bypass</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0706" rel="nofollow">CVE-2016-0706</a></p>
-
-<p>This issue only affects users running untrusted web applications under a
+ <p>This issue only affects users running untrusted web applications under a
security manager.</p>
-
-<p>The internal StatusManagerServlet could be loaded by a malicious web
+ <p>The internal StatusManagerServlet could be loaded by a malicious web
application when a security manager was configured. This servlet could
then provide the malicious web application with a list of all deployed
applications and a list of the HTTP request lines for all requests
@@ -1330,28 +656,20 @@
from other web applications, such as session IDs, to the web
application.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1722801">1722801</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1722801">1722801</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 27 December 2015
+ <p>This issue was identified by the Tomcat security team on 27 December 2015
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.67</p>
+ <p>Affects: 7.0.0 to 7.0.67</p>
-
-<p>
-<strong>Moderate: Security Manager bypass</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0714" rel="nofollow">CVE-2016-0714</a>
-</p>
+ <p><strong>Moderate: Security Manager bypass</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0714" rel="nofollow">CVE-2016-0714</a></p>
-
-<p>This issue only affects users running untrusted web applications under a
+ <p>This issue only affects users running untrusted web applications under a
security manager.</p>
-
-<p>Tomcat provides several session persistence mechanisms. The
+ <p>Tomcat provides several session persistence mechanisms. The
<code>StandardManager</code> persists session over a restart. The
<code>PersistentManager</code> is able to persist sessions to files, a
database or a custom <code>Store</code>. The cluster implementation
@@ -1362,69 +680,46 @@
session, a malicious web application could trigger the execution of
arbitrary code.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1726923">1726923</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1726923">1726923</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1727034">1727034</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 12 November 2015
+ <p>This issue was identified by the Tomcat security team on 12 November 2015
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.67</p>
+ <p>Affects: 7.0.0 to 7.0.67</p>
-
-<p>
-<strong>Moderate: Security Manager bypass</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0763" rel="nofollow">CVE-2016-0763</a>
-</p>
+ <p><strong>Moderate: Security Manager bypass</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0763" rel="nofollow">CVE-2016-0763</a></p>
-
-<p>This issue only affects users running untrusted web applications under a
+ <p>This issue only affects users running untrusted web applications under a
security manager.</p>
-
-<p>
-<code>ResourceLinkFactory.setGlobalContext()</code> is a public method
+ <p><code>ResourceLinkFactory.setGlobalContext()</code> is a public method
and was accessible to web applications even when running under a security
manager. This allowed a malicious web application to inject a malicious
global context that could in turn be used to disrupt other web
applications and/or read and write data owned by other web
applications.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1725931">1725931</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1725931">1725931</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 18 January 2016
+ <p>This issue was identified by the Tomcat security team on 18 January 2016
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.67</p>
+ <p>Affects: 7.0.0 to 7.0.67</p>
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.67"><span class="pull-right">10 December 2015</span> Fixed in Apache Tomcat 7.0.67</h3><div class="text">
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.67">
-<span class="pull-right">10 December 2015</span> Fixed in Apache Tomcat 7.0.67</h3>
-<div class="text">
-
-
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.66 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.66 but the
release vote for the 7.0.66 release candidate did not pass. Therefore,
although users must download 7.0.67 to obtain a version that includes a
fix for this issue, version 7.0.66 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>
-<strong>Low: Session Fixation</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346" rel="nofollow">CVE-2015-5346</a>
-</p>
+ <p><strong>Low: Session Fixation</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346" rel="nofollow">CVE-2015-5346</a></p>
-
-<p>When recycling the <code>Request</code> object to use for a new request,
+ <p>When recycling the <code>Request</code> object to use for a new request,
the <code>requestedSessionSSL</code> field was not recycled. This meant that
a session ID provided in the next request to be processed using the recycled
<code>Request</code> object could be used when it should not have been. This
@@ -1435,34 +730,22 @@
at least one web application to be configured to use the SSL session ID as
the HTTP session ID. This is not a common configuration.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1713187">1713187</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1713187">1713187</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 22 June 2014
+ <p>This issue was identified by the Tomcat security team on 22 June 2014
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.5 to 7.0.65</p>
+ <p>Affects: 7.0.5 to 7.0.65</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.65">
-<span class="pull-right">19 October 2015</span> Fixed in Apache Tomcat 7.0.65</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.65"><span class="pull-right">19 October 2015</span> Fixed in Apache Tomcat 7.0.65</h3><div class="text">
-
-<p>
-<strong>Low: Limited directory traversal</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5174" rel="nofollow">CVE-2015-5174</a>
-</p>
+ <p><strong>Low: Limited directory traversal</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5174" rel="nofollow">CVE-2015-5174</a></p>
-
-<p>This issue only affects users running untrusted web applications under a
+ <p>This issue only affects users running untrusted web applications under a
security manager.</p>
-
-<p>When accessing resources via the <code>ServletContext</code> methods
+ <p>When accessing resources via the <code>ServletContext</code> methods
<code>getResource()</code> <code>getResourceAsStream()</code> and
<code>getResourcePaths()</code> the paths should be limited to the
current web application. The validation was not correct and paths of the
@@ -1472,91 +755,58 @@
listing for the directory in which the web application had been deployed.
This should not be possible when running under a security manager.
Typically, the directory listing that would be exposed would be for
- <code>$CATALINA_BASE/webapps.</code>
-</p>
+ <code>$CATALINA_BASE/webapps.</code></p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1696284">1696284</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1696284">1696284</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1700898">1700898</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 12 August 2015
+ <p>This issue was identified by the Tomcat security team on 12 August 2015
and made public on 22 February 2016.</p>
-
-<p>Affects: 7.0.0 to 7.0.64</p>
-
+ <p>Affects: 7.0.0 to 7.0.64</p>
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.59">
-<span class="pull-right">4 February 2015</span> Fixed in Apache Tomcat 7.0.59</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.59"><span class="pull-right">4 February 2015</span> Fixed in Apache Tomcat 7.0.59</h3><div class="text">
-
-<p>
-<i>Note: The issue below was fixed in Apache Tomcat 7.0.58 but the
+ <p><i>Note: The issue below was fixed in Apache Tomcat 7.0.58 but the
release vote for the 7.0.58 release candidate did not pass. Therefore,
although users must download 7.0.59 to obtain a version that includes a
fix for this issue, versions 7.0.58 is not included in the list of
- affected versions.</i>
-</p>
+ affected versions.</i></p>
-
-<p>
-<strong>Moderate: Security Manager bypass</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7810" rel="nofollow">CVE-2014-7810</a>
-</p>
+ <p><strong>Moderate: Security Manager bypass</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7810" rel="nofollow">CVE-2014-7810</a></p>
-
-<p>Malicious web applications could use expression language to bypass the
+ <p>Malicious web applications could use expression language to bypass the
protections of a Security Manager as expressions were evaluated within a
privileged code section.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1644019">1644019</a> and
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1644019">1644019</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1645644">1645644</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 2 November 2014
+ <p>This issue was identified by the Tomcat security team on 2 November 2014
and made public on 14 May 2015.</p>
-
-<p>Affects: 7.0.0 to 7.0.57</p>
+ <p>Affects: 7.0.0 to 7.0.57</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.55">
-<span class="pull-right">27 July 2014</span> Fixed in Apache Tomcat 7.0.55</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.55"><span class="pull-right">27 July 2014</span> Fixed in Apache Tomcat 7.0.55</h3><div class="text">
-
-<p>
-<strong>Important: Request Smuggling</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0227" rel="nofollow">CVE-2014-0227</a>
-</p>
+ <p><strong>Important: Request Smuggling</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0227" rel="nofollow">CVE-2014-0227</a></p>
-
-<p>It was possible to craft a malformed chunk as part of a chunked request
+ <p>It was possible to craft a malformed chunk as part of a chunked request
that caused Tomcat to read part of the request body as a new request.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1601333">1601333</a>.</p>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1601333">1601333</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 30 May 2014
+ <p>This issue was identified by the Tomcat security team on 30 May 2014
and made public on 9 February 2015.</p>
-
-<p>Affects: 7.0.0 to 7.0.54</p>
+ <p>Affects: 7.0.0 to 7.0.54</p>
-
-<p>
-<strong>Low: Denial of Service</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0230" rel="nofollow">CVE-2014-0230</a>
-</p>
+ <p><strong>Low: Denial of Service</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0230" rel="nofollow">CVE-2014-0230</a></p>
-
-<p>When a response for a request with a request body is returned to the user
+ <p>When a response for a request with a request body is returned to the user
agent before the request body is fully read, by default Tomcat swallows the
remaining request body so that the next request on the connection may be
processed. There was no limit to the size of request body that Tomcat would
@@ -1564,34 +814,23 @@
close the connection and a processing thread would remain allocated to the
connection.</p>
-
-<p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1603781">1603781</a>
+ <p>This was fixed in revision <a href="https://svn.apache.org/viewvc?view=rev&rev=1603781">1603781</a>
and improved in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1603811">1603811</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1609176">1609176</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1659295">1659295</a>.</p>
-
-<p>This issue was disclosed to the Tomcat security team by AntBean@secdig
+ <p>This issue was disclosed to the Tomcat security team by AntBean@secdig
from the Baidu Security Team on 4 June 2014 and made public on 9 April
2015.</p>
-
-<p>Affects: 7.0.0 to 7.0.54</p>
+ <p>Affects: 7.0.0 to 7.0.54</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.54">
-<span class="pull-right">released 22 May 2014</span> Fixed in Apache Tomcat 7.0.54</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.54"><span class="pull-right">released 22 May 2014</span> Fixed in Apache Tomcat 7.0.54</h3><div class="text">
-
-<p>
-<strong>Low: Information Disclosure</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0119" rel="nofollow">CVE-2014-0119</a>
-</p>
+ <p><strong>Low: Information Disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0119" rel="nofollow">CVE-2014-0119</a></p>
-
-<p>In limited circumstances it was possible for a malicious web application
+ <p>In limited circumstances it was possible for a malicious web application
to replace the XML parsers used by Tomcat to process XSLTs for the
default servlet, JSP documents, tag library descriptors (TLDs) and tag
plugin configuration files. The injected XML parser(s) could then bypass
@@ -1599,246 +838,162 @@
XML files processed for other web applications deployed on the same
Tomcat instance.</p>
-
-<p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1588199">1588199</a>,
+ <p>This was fixed in revisions <a href="https://svn.apache.org/viewvc?view=rev&rev=1588199">1588199</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1589997">1589997</a>,
<a href="https://svn.apache.org/viewvc?view=rev&rev=1590028">1590028</a> and
<a href="https://svn.apache.org/viewvc?view=rev&rev=1590036">1590036</a>.</p>
-
-<p>This issue was identified by the Tomcat security team on 12 April 2014
+ <p>This issue was identified by the Tomcat security team on 12 April 2014
and made public on 27 May 2014.</p>
-
-<p>Affects: 7.0.0-7.0.53</p>
+ <p>Affects: 7.0.0-7.0.53</p>
-
-</div>
-<h3 id="Fixed_in_Apache_Tomcat_7.0.53">
-<span class="pull-right">released 30 Mar 2014</span> Fixed in Apache Tomcat 7.0.53</h3>
-<div class="text">
+ </div><h3 id="Fixed_in_Apache_Tomcat_7.0.53"><span class="pull-right">released 30 Mar 2014</span> Fixed in Apache Tomcat 7.0.53</h3><div class="text">
-
-<p>
-<strong>Important: Denial of Service</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0075" rel="nofollow">CVE-2014-0075</a>
-</p>
+ <p><strong>Important: Denial of Service</strong>
[... 1758 lines stripped ...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org