Author: markt
Date: Tue May 27 12:39:01 2014
New Revision: 1597764
URL: http://svn.apache.org/r1597764
Log:
CVE-2014-0075
CVE-2014-0095
CVE-2014-0096
CVE-2014-0099
CVE-2014-0119
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/xdocs/security-6.xml
tomcat/site/trunk/xdocs/security-7.xml
tomcat/site/trunk/xdocs/security-8.xml
Modified: tomcat/site/trunk/docs/security-6.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-6.html?rev=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-6.html (original)
+++ tomcat/site/trunk/docs/security-6.html Tue May 27 12:39:01 2014
@@ -200,6 +200,9 @@
<a href="#Apache_Tomcat_6.x_vulnerabilities">Apache Tomcat 6.x
vulnerabilities</a>
</li>
<li>
+<a href="#Fixed_in_Apache_Tomcat_6.0.41">Fixed in Apache Tomcat 6.0.41</a>
+</li>
+<li>
<a href="#Fixed_in_Apache_Tomcat_6.0.39">Fixed in Apache Tomcat 6.0.39</a>
</li>
<li>
@@ -300,6 +303,117 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_6.0.41">
+<span style="float: right;">released 2014-05-23</span> Fixed in Apache Tomcat
6.0.41</h3>
+<div class="text">
+
+
+<p>
+<i>Note: The issues below were fixed in Apache Tomcat 6.0.40 but the
+ release vote for the 6.0.40 release candidate did not pass.
+ Therefore, although users must download 6.0.41 to obtain a version that
+ includes fixes for these issues, version 6.0.40 is not
+ included in the list of affected versions.</i>
+</p>
+
+
+<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>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1579262";>1579262</a>.</p>
+
+
+<p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+
+<p>Affects: 6.0.0-6.0.39</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0096";
rel="nofollow">CVE-2014-0096</a>
+</p>
+
+
+<p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1585853";>1585853</a>.</p>
+
+
+<p>This issue was identified by the Tomcat security team on 27 February 2014
+ and made public on 27 May 2014.</p>
+
+
+<p>Affects: 6.0.0-6.0.39</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0099";
rel="nofollow">CVE-2014-0099</a>
+</p>
+
+
+<p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1580473";>1580473</a>.</p>
+
+
+<p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+
+<p>Affects: 6.0.0-6.0.39</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
+ 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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1593821";>1593821</a>.</p>
+
+
+<p>This issue was identified by the Tomcat security team on 12 April 2014
+ and made public on 27 May 2014.</p>
+
+
+<p>Affects: 6.0.0-6.0.39</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_6.0.39">
<span style="float: right;">released 31 January 2014</span> Fixed in Apache
Tomcat 6.0.39</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=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-7.html (original)
+++ tomcat/site/trunk/docs/security-7.html Tue May 27 12:39:01 2014
@@ -200,6 +200,12 @@
<a href="#Apache_Tomcat_7.x_vulnerabilities">Apache Tomcat 7.x
vulnerabilities</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>
@@ -314,6 +320,116 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_7.0.54">
+<span style="float: right;">released 2014-05-22</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>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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+
+<p>This was fixed in revisions <a
href="http://svn.apache.org/viewvc?view=rev&rev=1590028";>1590028</a> and
+ <a
href="http://svn.apache.org/viewvc?view=rev&rev=1589997";>1589997</a>.</p>
+
+
+<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>
+
+
+</div>
+<h3 id="Fixed_in_Apache_Tomcat_7.0.53">
+<span style="float: right;">released 2014-03-30</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>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578341";>1578341</a>.</p>
+
+
+<p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+
+<p>Affects: 7.0.0-7.0.52</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0096";
rel="nofollow">CVE-2014-0096</a>
+</p>
+
+
+<p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+
+<p>This was fixed in revisions <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578637";>1578637</a> and
+ <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578655";>1578655</a>.</p>
+
+
+<p>This issue was identified by the Tomcat security team on 27 February 2014
+ and made public on 27 May 2014.</p>
+
+
+<p>Affects: 7.0.0-7.0.52</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0099";
rel="nofollow">CVE-2014-0099</a>
+</p>
+
+
+<p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578814";>1578814</a>.</p>
+
+
+<p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+
+<p>Affects: 7.0.0-7.0.52</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_7.0.52">
<span style="float: right;">released 17 Feb 2014</span> Fixed in Apache Tomcat
7.0.52</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=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/docs/security-8.html (original)
+++ tomcat/site/trunk/docs/security-8.html Tue May 27 12:39:01 2014
@@ -200,6 +200,12 @@
<a href="#Apache_Tomcat_8.x_vulnerabilities">Apache Tomcat 8.x
vulnerabilities</a>
</li>
<li>
+<a href="#Fixed_in_Apache_Tomcat_8.0.8">Fixed in Apache Tomcat 8.0.8</a>
+</li>
+<li>
+<a href="#Fixed_in_Apache_Tomcat_8.0.5">Fixed in Apache Tomcat 8.0.5</a>
+</li>
+<li>
<a href="#Fixed_in_Apache_Tomcat_8.0.3">Fixed in Apache Tomcat 8.0.3</a>
</li>
<li>
@@ -260,6 +266,159 @@
</div>
+<h3 id="Fixed_in_Apache_Tomcat_8.0.8">
+<span style="float: right;">beta, 2014-05-21</span> Fixed in Apache Tomcat
8.0.8</h3>
+<div class="text">
+
+
+<p>
+<i>Note: The issue below was fixed in Apache Tomcat 8.0.6 but the
+ release votes for the 8.0.6 and 8.0.7 release candidates did not pass.
+ Therefore, although users must download 8.0.8 to obtain a version that
+ includes a fix for this issue, versions 8.0.6 and 8.0.7 are not
+ included in the list of affected versions.</i>
+</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
+ 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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+
+<p>This was fixed in revisions <a
href="http://svn.apache.org/viewvc?view=rev&rev=1589837";>1589837</a>,
+ <a
href="http://svn.apache.org/viewvc?view=rev&rev=1589980";>1589980</a> and
+ <a
href="http://svn.apache.org/viewvc?view=rev&rev=1589990";>1589990</a>.</p>
+
+
+<p>This issue was identified by the Tomcat security team on 12 April 2014
+ and made public on 27 May 2014.</p>
+
+
+<p>Affects: 8.0.0-RC1 to 8.0.5</p>
+
+
+</div>
+<h3 id="Fixed_in_Apache_Tomcat_8.0.5">
+<span style="float: right;">beta, 2014-03-27</span> Fixed in Apache Tomcat
8.0.5</h3>
+<div class="text">
+
+
+<p>
+<i>Note: The issues below were fixed in Apache Tomcat 8.0.4 but the
+ release vote for the 8.0.4 release candidate did not pass.
+ Therefore, although users must download 8.0.5 to obtain a version that
+ includes fixes for these issues, version 8.0.4 is not
+ included in the list of affected versions.</i>
+</p>
+
+
+<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>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578337";>1578337</a>.</p>
+
+
+<p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+
+<p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+
+<p>
+<strong>Important: Denial of Service</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0095";
rel="nofollow">CVE-2014-0095</a>
+</p>
+
+
+<p>A regression was introduced in <a
href="http://svn.apache.org/viewvc?view=rev&rev=1519838";>1519838</a>
+ that caused AJP requests to hang if an explicit content length of zero
+ was set on the request. The hanging request consumed a request
processing
+ thread which could lead to a denial of service.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578337";>1578337</a>.</p>
+
+
+<p>This issue was reported as a possible bug via the Tomcat users mailing
+ list on 3 March 2014 and the security implications were identified by
the
+ Tomcat security team on the same day. This issue was made public on 27
+ May 2014.</p>
+
+
+<p>Affects: 8.0.0-RC2 to 8.0.3</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0096";
rel="nofollow">CVE-2014-0096</a>
+</p>
+
+
+<p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+
+<p>This was fixed in revisions <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578610";>1578610</a> and
+ <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578611";>1578611</a>.</p>
+
+
+<p>This issue was identified by the Tomcat security team on 27 February 2014
+ and made public on 27 May 2014.</p>
+
+
+<p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+
+<p>
+<strong>Important: Information disclosure</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0099";
rel="nofollow">CVE-2014-0099</a>
+</p>
+
+
+<p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+
+<p>This was fixed in revision <a
href="http://svn.apache.org/viewvc?view=rev&rev=1578812";>1578812</a>.</p>
+
+
+<p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+
+<p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+
+</div>
<h3 id="Fixed_in_Apache_Tomcat_8.0.3">
<span style="float: right;">beta, 2014-02-11</span> Fixed in Apache Tomcat
8.0.3</h3>
<div class="text">
@@ -300,7 +459,7 @@
and accidently made public on 06 Feb 2014.</p>
-<p>Affects: 8.0.0-RC1-8.0.1</p>
+<p>Affects: 8.0.0-RC1 to 8.0.1</p>
</div>
Modified: tomcat/site/trunk/xdocs/security-6.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-6.xml?rev=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-6.xml (original)
+++ tomcat/site/trunk/xdocs/security-6.xml Tue May 27 12:39:01 2014
@@ -48,6 +48,83 @@
</section>
+ <section name="Fixed in Apache Tomcat 6.0.41" rtext="released 2014-05-23">
+
+ <p><i>Note: The issues below were fixed in Apache Tomcat 6.0.40 but the
+ release vote for the 6.0.40 release candidate did not pass.
+ Therefore, although users must download 6.0.41 to obtain a version that
+ includes fixes for these issues, version 6.0.40 is not
+ included in the list of affected versions.</i></p>
+
+ <p><strong>Important: Denial of Service</strong>
+ <cve>CVE-2014-0075</cve></p>
+
+ <p>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+ <p>This was fixed in revision <revlink rev="1579262">1579262</revlink>.</p>
+
+ <p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+ <p>Affects: 6.0.0-6.0.39</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0096</cve></p>
+
+ <p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+ <p>This was fixed in revision <revlink rev="1585853">1585853</revlink>.</p>
+
+ <p>This issue was identified by the Tomcat security team on 27 February
2014
+ and made public on 27 May 2014.</p>
+
+ <p>Affects: 6.0.0-6.0.39</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0099</cve></p>
+
+ <p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+ <p>This was fixed in revision <revlink rev="1580473">1580473</revlink>.</p>
+
+ <p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+ <p>Affects: 6.0.0-6.0.39</p>
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2014-0119</cve></p>
+
+ <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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+ <p>This was fixed in revision <revlink rev="1593821">1593821</revlink>.</p>
+
+ <p>This issue was identified by the Tomcat security team on 12 April 2014
+ and made public on 27 May 2014.</p>
+
+ <p>Affects: 6.0.0-6.0.39</p>
+
+ </section>
<section name="Fixed in Apache Tomcat 6.0.39" rtext="released 31 January
2014">
Modified: tomcat/site/trunk/xdocs/security-7.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-7.xml?rev=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-7.xml (original)
+++ tomcat/site/trunk/xdocs/security-7.xml Tue May 27 12:39:01 2014
@@ -50,6 +50,84 @@
</section>
+ <section name="Fixed in Apache Tomcat 7.0.54" rtext="released 2014-05-22">
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2014-0119</cve></p>
+
+ <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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+ <p>This was fixed in revisions <revlink rev="1590028">1590028</revlink> and
+ <revlink rev="1589997">1589997</revlink>.</p>
+
+ <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>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 7.0.53" rtext="released 2014-03-30">
+
+ <p><strong>Important: Denial of Service</strong>
+ <cve>CVE-2014-0075</cve></p>
+
+ <p>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+ <p>This was fixed in revision <revlink rev="1578341">1578341</revlink>.</p>
+
+ <p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+ <p>Affects: 7.0.0-7.0.52</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0096</cve></p>
+
+ <p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+ <p>This was fixed in revisions <revlink rev="1578637">1578637</revlink> and
+ <revlink rev="1578655">1578655</revlink>.</p>
+
+ <p>This issue was identified by the Tomcat security team on 27 February
2014
+ and made public on 27 May 2014.</p>
+
+ <p>Affects: 7.0.0-7.0.52</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0099</cve></p>
+
+ <p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+ <p>This was fixed in revision <revlink rev="1578814">1578814</revlink>.</p>
+
+ <p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+ <p>Affects: 7.0.0-7.0.52</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 7.0.52" rtext="released 17 Feb 2014">
<p><i>Note: The issue below was fixed in Apache Tomcat 7.0.51 but the
Modified: tomcat/site/trunk/xdocs/security-8.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-8.xml?rev=1597764&r1=1597763&r2=1597764&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/security-8.xml (original)
+++ tomcat/site/trunk/xdocs/security-8.xml Tue May 27 12:39:01 2014
@@ -50,6 +50,114 @@
</section>
+ <section name="Fixed in Apache Tomcat 8.0.8" rtext="beta, 2014-05-21">
+
+ <p><i>Note: The issue below was fixed in Apache Tomcat 8.0.6 but the
+ release votes for the 8.0.6 and 8.0.7 release candidates did not pass.
+ Therefore, although users must download 8.0.8 to obtain a version that
+ includes a fix for this issue, versions 8.0.6 and 8.0.7 are not
+ included in the list of affected versions.</i></p>
+
+ <p><strong>Low: Information Disclosure</strong>
+ <cve>CVE-2014-0119</cve></p>
+
+ <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
+ the limits imposed on XML external entities and/or have visibility of
the
+ XML files processed for other web applications deployed on the same
+ Tomcat instance.</p>
+
+ <p>This was fixed in revisions <revlink rev="1589837">1589837</revlink>,
+ <revlink rev="1589980">1589980</revlink> and
+ <revlink rev="1589990">1589990</revlink>.</p>
+
+ <p>This issue was identified by the Tomcat security team on 12 April 2014
+ and made public on 27 May 2014.</p>
+
+ <p>Affects: 8.0.0-RC1 to 8.0.5</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 8.0.5" rtext="beta, 2014-03-27">
+
+ <p><i>Note: The issues below were fixed in Apache Tomcat 8.0.4 but the
+ release vote for the 8.0.4 release candidate did not pass.
+ Therefore, although users must download 8.0.5 to obtain a version that
+ includes fixes for these issues, version 8.0.4 is not
+ included in the list of affected versions.</i></p>
+
+ <p><strong>Important: Denial of Service</strong>
+ <cve>CVE-2014-0075</cve></p>
+
+ <p>It was possible to craft a malformed chunk size as part of a chucked
+ request that enabled an unlimited amount of data to be streamed to the
+ server, bypassing the various size limits enforced on a request. This
+ enabled a denial of service attack.</p>
+
+ <p>This was fixed in revision <revlink rev="1578337">1578337</revlink>.</p>
+
+ <p>This issue was reported to the Tomcat security team by David Jorm of the
+ Red Hat Security Response Team on 28 February 2014 and made public on 27
+ May 2014.</p>
+
+ <p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+ <p><strong>Important: Denial of Service</strong>
+ <cve>CVE-2014-0095</cve></p>
+
+ <p>A regression was introduced in <revlink rev="1519838">1519838</revlink>
+ that caused AJP requests to hang if an explicit content length of zero
+ was set on the request. The hanging request consumed a request
processing
+ thread which could lead to a denial of service.</p>
+
+ <p>This was fixed in revision <revlink rev="1578337">1578337</revlink>.</p>
+
+ <p>This issue was reported as a possible bug via the Tomcat users mailing
+ list on 3 March 2014 and the security implications were identified by
the
+ Tomcat security team on the same day. This issue was made public on 27
+ May 2014.</p>
+
+ <p>Affects: 8.0.0-RC2 to 8.0.3</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0096</cve></p>
+
+ <p>The default servlet allows web applications to define (at multiple
+ levels) an XSLT to be used to format a directory listing. When running
+ under a security manager, the processing of these was not subject to the
+ same constraints as the web application. This enabled a malicious web
+ application to bypass the file access constraints imposed by the
security
+ manager via the use of external XML entities.</p>
+
+ <p>This was fixed in revisions <revlink rev="1578610">1578610</revlink> and
+ <revlink rev="1578611">1578611</revlink>.</p>
+
+ <p>This issue was identified by the Tomcat security team on 27 February
2014
+ and made public on 27 May 2014.</p>
+
+ <p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+ <p><strong>Important: Information disclosure</strong>
+ <cve>CVE-2014-0099</cve></p>
+
+ <p>The code used to parse the request content length header did not check
+ for overflow in the result. This exposed a request smuggling
+ vulnerability when Tomcat was located behind a reverse proxy that
+ correctly processed the content length header.</p>
+
+ <p>This was fixed in revision <revlink rev="1578812">1578812</revlink>.</p>
+
+ <p>A test case that demonstrated the parsing bug was sent to the Tomcat
+ security team on 13 March 2014 but no context was provided. The security
+ implications were identified by the Tomcat security team the day the
+ report was received and made public on 27 May 2014.</p>
+
+ <p>Affects: 8.0.0-RC1 to 8.0.3</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 8.0.3" rtext="beta, 2014-02-11">
<p><i>Note: The issue below was fixed in Apache Tomcat 8.0.2 but the
@@ -77,7 +185,7 @@
<p>This issue was reported to the Apache Software Foundation on 04 Feb 2014
and accidently made public on 06 Feb 2014.</p>
- <p>Affects: 8.0.0-RC1-8.0.1</p>
+ <p>Affects: 8.0.0-RC1 to 8.0.1</p>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
