SCIENTIFIC-LINUX-ERRATA Archives

July 2014

SCIENTIFIC-LINUX-ERRATA@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Pat Riehecky <[log in to unmask]>
Reply To:
Date:
Wed, 9 Jul 2014 18:16:17 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines)
Synopsis:          Moderate: tomcat6 security and bug fix update
Advisory ID:       SLSA-2014:0865-1
Issue Date:        2014-07-09
CVE Numbers:       CVE-2014-0075
                   CVE-2014-0096
                   CVE-2014-0099
--

It was discovered that Apache Tomcat did not limit the length of chunk
sizes when using chunked transfer encoding. A remote attacker could use
this flaw to perform a denial of service attack against Tomcat by
streaming an unlimited quantity of data, leading to excessive consumption
of server resources. (CVE-2014-0075)

It was found that Apache Tomcat did not check for overflowing values when
parsing request content length headers. A remote attacker could use this
flaw to perform an HTTP request smuggling attack on a Tomcat server
located behind a reverse proxy that processed the content length header
correctly. (CVE-2014-0099)

It was found that the org.apache.catalina.servlets.DefaultServlet
implementation in Apache Tomcat allowed the definition of XML External
Entities (XXEs) in provided XSLTs. A malicious application could use this
to circumvent intended security restrictions to disclose sensitive
information. (CVE-2014-0096)

This update also fixes the following bugs:

* The patch that resolved the CVE-2014-0050 issue contained redundant
code. This update removes the redundant code.

* The patch that resolved the CVE-2013-4322 issue contained an invalid
check that triggered a java.io.EOFException while reading trailer headers
for chunked requests. This update fixes the check and the aforementioned
exception is no longer triggered in the described scenario.

Tomcat must be restarted for this update to take effect.
--

SL6
  x86_64
    tomcat6-javadoc-6.0.24-72.el6_5.noarch.rpm
    tomcat6-6.0.24-72.el6_5.noarch.rpm
    tomcat6-webapps-6.0.24-72.el6_5.noarch.rpm
    tomcat6-servlet-2.5-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-jsp-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-docs-webapp-6.0.24-72.el6_5.noarch.rpm
    tomcat6-el-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-lib-6.0.24-72.el6_5.noarch.rpm
    tomcat6-admin-webapps-6.0.24-72.el6_5.noarch.rpm
  i386
    tomcat6-javadoc-6.0.24-72.el6_5.noarch.rpm
    tomcat6-6.0.24-72.el6_5.noarch.rpm
    tomcat6-webapps-6.0.24-72.el6_5.noarch.rpm
    tomcat6-servlet-2.5-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-jsp-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-docs-webapp-6.0.24-72.el6_5.noarch.rpm
    tomcat6-el-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-lib-6.0.24-72.el6_5.noarch.rpm
    tomcat6-admin-webapps-6.0.24-72.el6_5.noarch.rpm
  srpm
    tomcat6-6.0.24-72.el6_5.src.rpm
  noarch
    tomcat6-6.0.24-72.el6_5.noarch.rpm
    tomcat6-admin-webapps-6.0.24-72.el6_5.noarch.rpm
    tomcat6-docs-webapp-6.0.24-72.el6_5.noarch.rpm
    tomcat6-el-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-javadoc-6.0.24-72.el6_5.noarch.rpm
    tomcat6-jsp-2.1-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-lib-6.0.24-72.el6_5.noarch.rpm
    tomcat6-servlet-2.5-api-6.0.24-72.el6_5.noarch.rpm
    tomcat6-webapps-6.0.24-72.el6_5.noarch.rpm

- Scientific Linux Development Team

ATOM RSS1 RSS2