You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2017/04/10 19:14:17 UTC
svn commit: r1790883 - in /tomcat/site/trunk: docs/security-6.html
docs/security-7.html docs/security-8.html docs/security-9.html
xdocs/security-6.xml xdocs/security-7.xml xdocs/security-8.xml
xdocs/security-9.xml
Author: markt
Date: Mon Apr 10 19:14:17 2017
New Revision: 1790883
URL: http://svn.apache.org/viewvc?rev=1790883&view=rev
Log:
Announcements for
- CVE-2017-5651
- CVE-2017-5650
- CVE-2017-5647
- CVE-2017-5648
Modified:
tomcat/site/trunk/docs/security-6.html
tomcat/site/trunk/docs/security-7.html
tomcat/site/trunk/docs/security-8.html
tomcat/site/trunk/docs/security-9.html
tomcat/site/trunk/xdocs/security-6.xml
tomcat/site/trunk/xdocs/security-7.xml
tomcat/site/trunk/xdocs/security-8.xml
tomcat/site/trunk/xdocs/security-9.xml
Modified: tomcat/site/trunk/docs/security-6.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-6.html?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-6.html (original)
+++ tomcat/site/trunk/docs/security-6.html Mon Apr 10 19:14:17 2017
@@ -227,6 +227,9 @@
<a href="#Apache_Tomcat_6.x_vulnerabilities">Apache Tomcat 6.x vulnerabilities</a>
</li>
<li>
+<a href="#Fixed_in_Apache_Tomcat_6.0.53">Fixed in Apache Tomcat 6.0.53</a>
+</li>
+<li>
<a href="#Fixed_in_Apache_Tomcat_6.0.50">Fixed in Apache Tomcat 6.0.50</a>
</li>
<li>
@@ -348,6 +351,38 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_6.0.53">
+<span style="float: right;">7 April 2017</span> Fixed in Apache Tomcat 6.0.53</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
+ 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 revisions <a href="http://svn.apache.org/viewvc?view=rev&rev=1789024">1789024</a>,
+ <a href="http://svn.apache.org/viewvc?view=rev&rev=1789155">1789155</a>
+ and <a href="http://svn.apache.org/viewvc?view=rev&rev=1789856">1789856</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: 6.0.0 to 6.0.52</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_6.0.50">
<span style="float: right;">not yet released</span> Fixed in Apache Tomcat 6.0.50</h3>
<div class="text">
Modified: tomcat/site/trunk/docs/security-7.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-7.html?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-7.html (original)
+++ tomcat/site/trunk/docs/security-7.html Mon Apr 10 19:14:17 2017
@@ -227,6 +227,12 @@
<a href="#Apache_Tomcat_7.x_vulnerabilities">Apache Tomcat 7.x vulnerabilities</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>
@@ -374,6 +380,66 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_7.0.77">
+<span style="float: 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>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&rev=1789008">1789008</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: 7.0.0 to 7.0.76</p>
+
+
+</div>
+<h3 id="Fixed_in_Apache_Tomcat_7.0.76">
+<span style="float: 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>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&rev=1785777">1785777</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: 7.0.0 to 7.0.75</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_7.0.75">
<span style="float: right;">24 January 2017</span> Fixed in Apache Tomcat 7.0.75</h3>
<div class="text">
Modified: tomcat/site/trunk/docs/security-8.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-8.html?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-8.html (original)
+++ tomcat/site/trunk/docs/security-8.html Mon Apr 10 19:14:17 2017
@@ -227,12 +227,24 @@
<a href="#Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x vulnerabilities</a>
</li>
<li>
-<a href="#Fixed_in_Apache_Tomcat_8.5.11">Fixed in Apache Tomcat 8.5.11</a>
+<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>
@@ -329,41 +341,171 @@
</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>
+<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
+ 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&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>
-<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>
+<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
+ 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&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>
+ <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
+ 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&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>
+ <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
+ 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&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>Moderate: Information Disclosure</strong>
- <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8747" rel="nofollow">CVE-2016-8747</a>
+<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>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>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&rev=1774166">1774166</a>.</p>
+<p>This was fixed in revision <a href="http://svn.apache.org/viewvc?view=rev&rev=1785776">1785776</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>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.7 to 8.5.9</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>
+ <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
+ 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&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>
@@ -406,6 +548,44 @@
</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>
+ <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
+ 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&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">
Modified: tomcat/site/trunk/docs/security-9.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-9.html?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-9.html (original)
+++ tomcat/site/trunk/docs/security-9.html Mon Apr 10 19:14:17 2017
@@ -227,6 +227,12 @@
<a href="#Apache_Tomcat_9.x_vulnerabilities">Apache Tomcat 9.x vulnerabilities</a>
</li>
<li>
+<a href="#Fixed_in_Apache_Tomcat_9.0.0.M19">Fixed in Apache Tomcat 9.0.0.M19</a>
+</li>
+<li>
+<a href="#Fixed_in_Apache_Tomcat_9.0.0.M18">Fixed in Apache Tomcat 9.0.0.M18</a>
+</li>
+<li>
<a href="#Fixed_in_Apache_Tomcat_9.0.0.M17">Fixed in Apache Tomcat 9.0.0.M17</a>
</li>
<li>
@@ -293,6 +299,114 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_9.0.0.M19">
+<span style="float: right;">30 March 2017</span> Fixed in Apache Tomcat 9.0.0.M19</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
+ 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&rev=1788544">1788544</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: 9.0.0.M1 to 9.0.0.M18</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
+ 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&rev=1788460">1788460</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: 9.0.0.M1 to 9.0.0.M18</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
+ 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&rev=1788890">1788890</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: 9.0.0.M1 to 9.0.0.M18</p>
+
+
+</div>
+<h3 id="Fixed_in_Apache_Tomcat_9.0.0.M18">
+<span style="float: right;">13 March 2017</span> Fixed in Apache Tomcat 9.0.0.M18</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
+ 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&rev=1785774">1785774</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: 9.0.0.M1 to 9.0.0.M17</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_9.0.0.M17">
<span style="float: right;">16 January 2017</span> Fixed in Apache Tomcat 9.0.0.M17</h3>
<div class="text">
Modified: tomcat/site/trunk/xdocs/security-6.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-6.xml?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-6.xml (original)
+++ tomcat/site/trunk/xdocs/security-6.xml Mon Apr 10 19:14:17 2017
@@ -48,6 +48,29 @@
</section>
+ <section name="Fixed in Apache Tomcat 6.0.53" rtext="7 April 2017">
+
+ <p><strong>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5647</cve></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 revisions <revlink rev="1789024">1789024</revlink>,
+ <revlink rev="1789155">1789155</revlink>
+ and <revlink rev="1789856">1789856</revlink>.</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: 6.0.0 to 6.0.52</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 6.0.50" rtext="not yet released">
<p><i>Note: The issue below was fixed in Apache Tomcat 6.0.49 but the
Modified: tomcat/site/trunk/xdocs/security-7.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-7.xml?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-7.xml (original)
+++ tomcat/site/trunk/xdocs/security-7.xml Mon Apr 10 19:14:17 2017
@@ -50,6 +50,48 @@
</section>
+ <section name="Fixed in Apache Tomcat 7.0.77" rtext="2 April 2017">
+
+ <p><strong>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5647</cve></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 <revlink rev="1789008">1789008</revlink>.</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: 7.0.0 to 7.0.76</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 7.0.76" rtext="16 March 2017">
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2017-5648</cve></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 <revlink rev="1785777">1785777</revlink>.</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: 7.0.0 to 7.0.75</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 7.0.75" rtext="24 January 2017">
<p><strong>Important: Information Disclosure</strong>
Modified: tomcat/site/trunk/xdocs/security-8.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-8.xml?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-8.xml (original)
+++ tomcat/site/trunk/xdocs/security-8.xml Mon Apr 10 19:14:17 2017
@@ -50,29 +50,121 @@
</section>
- <section name="Fixed in Apache Tomcat 8.5.11" rtext="16 January 2017">
+ <section name="Fixed in Apache Tomcat 8.0.43" rtext="2 April 2017">
- <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>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5647</cve></p>
- <p><strong>Moderate: Information Disclosure</strong>
- <cve>CVE-2016-8747</cve></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>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 <revlink rev="1788999">1788999</revlink>.</p>
- <p>This was fixed in revision <revlink rev="1774166">1774166</revlink>.</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>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.0.0.RC1 to 8.0.42</p>
- <p>Affects: 8.5.7 to 8.5.9</p>
+ </section>
+
+ <section name="Fixed in Apache Tomcat 8.5.13" rtext="30 March 2017">
+
+ <p><strong>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5651</cve></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 <revlink rev="1788546">1788546</revlink>.</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>
+ <cve>CVE-2017-5650</cve></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 <revlink rev="1788480">1788480</revlink>.</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>
+ <cve>CVE-2017-5647</cve></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 <revlink rev="1788932">1788932</revlink>.</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>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 8.0.42" rtext="14 March 2017">
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2017-5648</cve></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 <revlink rev="1785776">1785776</revlink>.</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>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 8.5.12" rtext="13 March 2017">
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2017-5648</cve></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 <revlink rev="1785775">1785775</revlink>.</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>
</section>
@@ -103,6 +195,32 @@
</section>
+ <section name="Fixed in Apache Tomcat 8.5.11" rtext="16 January 2017">
+
+ <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>
+ <cve>CVE-2016-8747</cve></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 <revlink rev="1774166">1774166</revlink>.</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>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 8.5.9" rtext="8 December 2016">
<p><strong>Important: Information Disclosure</strong>
Modified: tomcat/site/trunk/xdocs/security-9.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-9.xml?rev=1790883&r1=1790882&r2=1790883&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-9.xml (original)
+++ tomcat/site/trunk/xdocs/security-9.xml Mon Apr 10 19:14:17 2017
@@ -50,6 +50,82 @@
</section>
+ <section name="Fixed in Apache Tomcat 9.0.0.M19" rtext="30 March 2017">
+
+ <p><strong>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5651</cve></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 <revlink rev="1788544">1788544</revlink>.</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: 9.0.0.M1 to 9.0.0.M18</p>
+
+ <p><strong>Important: Denial of Service</strong>
+ <cve>CVE-2017-5650</cve></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 <revlink rev="1788460">1788460</revlink>.</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: 9.0.0.M1 to 9.0.0.M18</p>
+
+ <p><strong>Important: Information Disclosure</strong>
+ <cve>CVE-2017-5647</cve></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 <revlink rev="1788890">1788890</revlink>.</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: 9.0.0.M1 to 9.0.0.M18</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 9.0.0.M18" rtext="13 March 2017">
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2017-5648</cve></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 <revlink rev="1785774">1785774</revlink>.</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: 9.0.0.M1 to 9.0.0.M17</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 9.0.0.M17" rtext="16 January 2017">
<p><i>Note: The issue below was fixed in Apache Tomcat 9.0.0.M16 but the
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org