org.apache.tomcat.embed:tomcat-embed-core@8.0.0-RC3 vulnerabilities
-
latest version
10.1.20
-
latest non vulnerable version
-
first published
14 years ago
-
latest version published
2 months ago
-
licenses detected
- [0,)
-
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.tomcat.embed:tomcat-embed-core package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.| Vulnerability | Vulnerable Version |
|---|---|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Denial of Service (DoS) in the implementation of the HTTP/2 protocol. An attacker can cause a denial of service (including via DDoS) by rapidly resetting many streams through request cancellation. How to fix Denial of Service (DoS)? Upgrade |
[,8.5.94)
[9.0.0,9.0.81)
[10.0.0,10.1.14)
[11.0.0-M3,11.0.0-M12)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Access Restriction Bypass. The URL pattern of (the empty string) which exactly maps to the context root was not correctly handled, 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. How to fix Access Restriction Bypass? Upgrade |
[7.0.0,7.0.85)
[8.0.0.RC1,8.0.50)
[8.5.0,8.5.28)
[9.0.0.M1,9.0.5)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Directory Traversal. 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. How to fix Directory Traversal? Upgrade |
[9.0.0M1,9.0.5)
[8.5.0,8.5.28)
[8.0.0RC1,8.0.50)
[7.0.0,7.0.85)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Access Restriction Bypass. 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 9.0.0.M1 to 9.0.0.M20, 8.5.0 to 8.5.14, 8.0.0.RC1 to 8.0.43 and 7.0.0 to 7.0.77 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. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. (2) By default, the response generated by a Servlet does depend on the HTTP method. Custom Servlets used as error pages must ensure that they handle any error dispatch as a GET request, regardless of the actual method. How to fix Access Restriction Bypass? Upgrade |
[7.0.0,7.0.78)
[8.0.0RC1,8.0.44)
[8.5.0,8.5.15)
[9.0.0.M1,9.0.0.M21)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Information Exposure. A bug in the handling of the pipelined requests, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C. How to fix Information Exposure? Upgrade |
[7.0.0,7.0.77)
[8.0.0-RC1,8.0.43)
[8.5.0,8.5.13)
[9.0.0.M1,9.0.0.M19)
|
Affected versions of this package are vulnerable to Information Disclosure. While investigating bug 60718, it was noticed that some calls to application listeners, It did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application. How to fix Information Exposure? Upgrade |
[7.0.0,7.0.76)
[8.0.0-RC1,8.0.42)
[8.5.0,8.5.12)
[9.0.0.M1,9.0.0.M17)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Information Exposure. The refactoring of the Connector code for 8.5.x onwards introduced a regression in the error handling of the send file code for the NIO HTTP connector. An error during send file processing resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. How to fix Information Exposure? Upgrade |
[7,7.0.74)
[8.5.0,8.5.9)
[8.0.0RC1,8.0.40)
[9.0.0M1,9.0.0M15)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Timing Attack. The How to fix Timing Attack? Upgrade |
[7.0.0,7.0.72)
[8.0.0-RC1,8.0.37)
[8.5.0,8.5.5)
[9.0.0.M1,9.0.0.M10)
|
|
[7.0.0,7.0.66)
[8.0.0-RC1,8.0.30)
[9.0.0.M1,9.0.0.M2)
|
|
[7.0.0,7.0.68)
[8.0.0-RC1,8.0.32)
[9.0.0.M1,9.0.0.M3)
|
|
[7.0.0,7.0.68)
[8.0.0-RC1,8.0.32)
[9.0.0.M1,9.0.0.M3)
|
|
[7.0.0,7.0.68)
[8.0.0-RC1,8.0.30)
[9.0.0.M1,9.0.0.M2)
|
|
[7.0.0,7.0.68)
[8.0.0-RC1,8.0.32)
[9.0.0.M1,9.0.0.M3)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Improper Access Control. It does not properly consider the possibility of an accessible interface implemented by an inaccessible class, which allows attackers to bypass a SecurityManager protection mechanism via a web application that leverages use of incorrect privileges during EL evaluation. How to fix Improper Access Control? Upgrade |
[7.0.0,7.0.58)
[8.0.0-RC1,8.0.16)
|
|
[7.0.0,7.0.55)
[8.0.0-RC1,8.0.9)
|
|
[7.0.0,7.0.53)
[8.0.0-RC1,8.0.4)
|
org.apache.tomcat.embed:tomcat-embed-core is a Core Tomcat implementation. Affected versions of this package are vulnerable to Arbitrary File Read. Apache Tomcat before 6.0.40, 7.x before 7.0.54, and 8.x before 8.0.6 does not properly constrain the class loader that accesses the XML parser used with an XSLT stylesheet, which allows remote attackers to (1) read arbitrary files via a crafted web application that provides an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, or (2) read files associated with different web applications on a single Tomcat instance via a crafted web application. How to fix Arbitrary File Read? Upgrade |
[7.0.0,7.0.54)
[8.0.0-RC1,8.0.6)
|