Search for packages
| purl | pkg:deb/debian/tomcat8@8.0.14-1~bpo70%2B2 |
| Next non-vulnerable version | 8.5.54-0+deb9u1 |
| Latest non-vulnerable version | 8.5.54-0+deb9u1 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1fkk-yntx-hyfd
Aliases: CVE-2020-1938 GHSA-c9hw-wf7x-jp9j |
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations. |
Affected by 0 other vulnerabilities. |
|
VCID-3e67-m39j-euaj
Aliases: CVE-2017-6056 |
Affected by 16 other vulnerabilities. |
|
|
VCID-6h37-5spb-nudp
Aliases: CVE-2016-0706 GHSA-6vx3-hr43-cfrh |
Affected by 16 other vulnerabilities. |
|
|
VCID-7b1n-ck2m-rbfu
Aliases: CVE-2017-5647 GHSA-3gv7-3h64-78cm |
Affected by 16 other vulnerabilities. |
|
|
VCID-7n44-6sjn-kufk
Aliases: CVE-2018-11784 GHSA-5q99-f34m-67gc |
When the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 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. |
Affected by 0 other vulnerabilities. |
|
VCID-7qa1-psnz-sffk
Aliases: CVE-2016-9775 |
Affected by 16 other vulnerabilities. |
|
|
VCID-97nc-3edh-9qdx
Aliases: CVE-2019-0221 GHSA-jjpq-gp5q-8q6w |
The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website. |
Affected by 0 other vulnerabilities. |
|
VCID-a275-x6jy-eybe
Aliases: CVE-2015-5351 GHSA-w7cg-5969-678w |
Affected by 16 other vulnerabilities. |
|
|
VCID-anxt-ts7w-wye1
Aliases: CVE-2019-17563 GHSA-9xcj-c8cr-8c3c |
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability. |
Affected by 0 other vulnerabilities. |
|
VCID-aycw-nzkw-buhj
Aliases: CVE-2019-12418 GHSA-hh3j-x4mc-g48r |
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance. |
Affected by 0 other vulnerabilities. |
|
VCID-bb3d-fmzb-t3c2
Aliases: CVE-2016-1240 |
Affected by 16 other vulnerabilities. |
|
|
VCID-c5rh-arx1-dfbj
Aliases: CVE-2016-5018 GHSA-4v3g-g84w-hv7r |
Affected by 16 other vulnerabilities. |
|
|
VCID-cyky-7kzu-nba5
Aliases: CVE-2016-0762 GHSA-wxcp-f2c8-x6xv |
Affected by 16 other vulnerabilities. |
|
|
VCID-dd8q-m5rh-fuhw
Aliases: CVE-2016-6794 GHSA-2rvf-329f-p99g |
Affected by 16 other vulnerabilities. |
|
|
VCID-ek4u-ssqw-77cv
Aliases: CVE-2015-5346 GHSA-jrcp-c39h-r29x |
Affected by 16 other vulnerabilities. |
|
|
VCID-fm4m-zurr-hyht
Aliases: CVE-2014-7810 GHSA-4c43-cwvx-9crh |
Affected by 16 other vulnerabilities. |
|
|
VCID-j52h-jxrq-43g1
Aliases: CVE-2016-6816 GHSA-jc7p-5r39-9477 |
Affected by 16 other vulnerabilities. |
|
|
VCID-j8tv-cs47-93h9
Aliases: CVE-2018-8014 GHSA-r4x2-3cq5-hqvp |
The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue. |
Affected by 0 other vulnerabilities. |
|
VCID-kcvp-2brm-p7f2
Aliases: CVE-2015-5174 GHSA-6qr6-x7jm-x2q6 |
Affected by 16 other vulnerabilities. |
|
|
VCID-ks1b-8a8q-bker
Aliases: CVE-2018-8034 GHSA-46j3-r4pj-4835 |
The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88. |
Affected by 0 other vulnerabilities. |
|
VCID-kuap-mmfh-jyhr
Aliases: CVE-2016-8735 GHSA-cw54-59pw-4g8c |
Affected by 16 other vulnerabilities. |
|
|
VCID-nq3y-spqj-qyca
Aliases: CVE-2018-1305 GHSA-jx6h-3fjx-cgv5 |
Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 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. |
Affected by 0 other vulnerabilities. |
|
VCID-nxhv-dzkd-cfcb
Aliases: CVE-2016-0763 GHSA-9hjv-9h75-xmpp |
Affected by 16 other vulnerabilities. |
|
|
VCID-pb38-eqgs-4ug7
Aliases: CVE-2019-17569 GHSA-767j-jfh2-jvrc |
The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely. |
Affected by 0 other vulnerabilities. |
|
VCID-pjr4-ssvt-cfge
Aliases: DSA-3788-2 tomcat8 |
regression update |
Affected by 16 other vulnerabilities. |
|
VCID-s2yw-ayf9-gfgp
Aliases: CVE-2017-5648 GHSA-3vx3-xf6q-r5xp |
Affected by 16 other vulnerabilities. |
|
|
VCID-snze-gjzq-dudy
Aliases: CVE-2017-7674 GHSA-73rx-3f9r-x949 |
Affected by 16 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
|
VCID-t538-646q-pqf4
Aliases: CVE-2018-1336 GHSA-m59c-jpc8-m2x4 |
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. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86. |
Affected by 0 other vulnerabilities. |
|
VCID-ufdf-fh63-7ye7
Aliases: CVE-2016-6796 GHSA-3mjp-p938-4329 |
Affected by 16 other vulnerabilities. |
|
|
VCID-uy2u-497k-y7fh
Aliases: CVE-2017-5664 GHSA-jmvv-524f-hj5j |
Affected by 16 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
|
VCID-w38v-t8zm-mfdc
Aliases: CVE-2016-0714 GHSA-mv42-px54-87jw |
Affected by 16 other vulnerabilities. |
|
|
VCID-w67f-7ck2-83e2
Aliases: CVE-2016-8745 GHSA-w3j5-q8f2-3cqq |
Affected by 16 other vulnerabilities. |
|
|
VCID-x36b-25k2-ckcx
Aliases: CVE-2020-1935 GHSA-qxf4-chvg-4r8r |
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely. |
Affected by 0 other vulnerabilities. |
|
VCID-xu7t-p6w1-4ycd
Aliases: CVE-2018-1304 GHSA-6rxj-58jh-436r |
The URL pattern of "" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 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. |
Affected by 0 other vulnerabilities. |
|
VCID-yazq-9973-9kab
Aliases: CVE-2016-9774 |
Affected by 16 other vulnerabilities. |
|
|
VCID-ytwn-k91p-y7ht
Aliases: CVE-2015-5345 GHSA-rh8q-vjgf-gf74 |
Affected by 16 other vulnerabilities. |
|
|
VCID-yvgh-9bh8-c7f5
Aliases: CVE-2016-3092 GHSA-fvm3-cfvj-gxqq |
Affected by 16 other vulnerabilities. |
|
|
VCID-zga5-ukcv-7khq
Aliases: CVE-2016-6797 GHSA-q6x7-f33r-3wxx |
Affected by 16 other vulnerabilities. |
|
|
VCID-znaw-aejz-u7ba
Aliases: CVE-2019-0199 GHSA-qcxh-w3j9-58qr |
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS. |
Affected by 0 other vulnerabilities. |
|
VCID-zwc5-6mks-4ked
Aliases: CVE-2018-8037 GHSA-6v52-mj5r-7j2m |
If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||