Import Debian changes 8.0.14-1+deb8u14
tomcat8 (8.0.14-1+deb8u14) jessie-security; urgency=high * Non-maintainer upload by the LTS team. * Fix CVE-2018-11784: Sergey Bobrov discovered that when the default servlet returned a redirect to a directory (e.g. redirecting to /foo/ when the user requested /foo) a specially crafted URL could be used to cause the redirect to be generated to any URI of the attackers choice. tomcat8 (8.0.14-1+deb8u13) jessie-security; urgency=high * Non-maintainer upload by the LTS Team. * Fix CVE-2018-1336: 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. * Fix CVE-2018-8034: The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. tomcat8 (8.0.14-1+deb8u12) jessie-security; urgency=high * Non-maintainer upload by the LTS Team. * Refreshed the expired SSL certificates used by the tests * Fix CVE-2018-1304: 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. (Closes: #802312) * Fix CVE-2018-1305: 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. (Closes: #802312) tomcat8 (8.0.14-1+deb8u11) jessie-security; urgency=high * Fix CVE-2017-7674: 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. tomcat8 (8.0.14-1+deb8u10) jessie-security; urgency=high * Team upload. * Fix CVE-2017-5664. 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. 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. The Default Servlet in Apache Tomcat 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. (Closes: #864447)
Loading
Please register or sign in to comment