- -------------------------------------------------------------------------
Debian Security Advisory DSA-3788-2                   security@debian.org
https://www.debian.org/security/                     Salvatore Bonaccorso
February 22, 2017                     https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : tomcat8

The update for tomcat8 issued as DSA-3788-1 caused that the server could
return HTTP 400 errors under certain circumstances. Updated packages are
now available to correct this issue. For reference, the original
advisory text follows.

It was discovered that a programming error in the processing of HTTPS
requests in the Apache Tomcat servlet and JSP engine may result in
denial of service via an infinite loop.

For the stable distribution (jessie), this problem has been fixed in
version 8.0.14-1+deb8u8.

We recommend that you upgrade your tomcat8 packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org

Debian: DSA-3788-2: tomcat8 regression update

February 22, 2017
The update for tomcat8 issued as DSA-3788-1 caused that the server could return HTTP 400 errors under certain circumstances

Summary

It was discovered that a programming error in the processing of HTTPS
requests in the Apache Tomcat servlet and JSP engine may result in
denial of service via an infinite loop.

For the stable distribution (jessie), this problem has been fixed in
version 8.0.14-1+deb8u8.

We recommend that you upgrade your tomcat8 packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org

Severity
The update for tomcat8 issued as DSA-3788-1 caused that the server could
return HTTP 400 errors under certain circumstances. Updated packages are
now available to correct this issue. For reference, the original
advisory text follows.

Related News