CVE-2017-5664High· 7.5▾ TwilightThe 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 tha…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 3.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
17%
— → 7.5
none → high
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.
tomcat = 7.0.0tomcat = 7.0.1tomcat = 7.0.2tomcat = 7.0.3tomcat = 7.0.4tomcat = 7.0.5tomcat = 7.0.6tomcat = 7.0.7tomcat = 7.0.8tomcat = 7.0.9tomcat = 7.0.10tomcat = 7.0.11tomcat = 7.0.12tomcat = 7.0.13tomcat = 7.0.14tomcat = 7.0.15tomcat = 7.0.16tomcat = 7.0.17tomcat = 7.0.18tomcat = 7.0.19tomcat = 7.0.20tomcat = 7.0.21tomcat = 7.0.22tomcat = 7.0.23tomcat = 7.0.24tomcat = 7.0.25tomcat = 7.0.26tomcat = 7.0.27tomcat = 7.0.28tomcat = 7.0.29tomcat = 7.0.30tomcat = 7.0.31tomcat = 7.0.32tomcat = 7.0.33tomcat = 7.0.34tomcat = 7.0.35tomcat = 7.0.36tomcat = 7.0.37tomcat = 7.0.38tomcat = 7.0.39tomcat = 7.0.40tomcat = 7.0.41tomcat = 7.0.42tomcat = 7.0.43tomcat = 7.0.44tomcat = 7.0.45tomcat = 7.0.46tomcat = 7.0.47tomcat = 7.0.48tomcat = 7.0.49tomcat = 7.0.50tomcat = 7.0.51tomcat = 7.0.54tomcat = 7.0.55tomcat = 7.0.56tomcat = 7.0.57tomcat = 7.0.58tomcat = 7.0.59tomcat = 7.0.60tomcat = 7.0.61tomcat = 7.0.62tomcat = 7.0.63tomcat = 7.0.64tomcat = 7.0.65tomcat = 7.0.66tomcat = 7.0.67tomcat = 7.0.68tomcat = 7.0.69tomcat = 7.0.70tomcat = 7.0.71tomcat = 7.0.72tomcat = 7.0.73tomcat = 7.0.74tomcat = 7.0.75tomcat = 7.0.76tomcat = 7.0.77tomcat = 8.0.0tomcat = 8.0.1tomcat = 8.0.2tomcat = 8.0.3tomcat = 8.0.4tomcat = 8.0.5tomcat = 8.0.6tomcat = 8.0.7tomcat = 8.0.9tomcat = 8.0.10tomcat = 8.0.11tomcat = 8.0.12tomcat = 8.0.13tomcat = 8.0.14tomcat = 8.0.15tomcat = 8.0.16tomcat = 8.0.17tomcat = 8.0.18tomcat = 8.0.19tomcat = 8.0.20tomcat = 8.0.21tomcat = 8.0.22tomcat = 8.0.23tomcat = 8.0.24Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2018-11784Medium· 4.3When 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
CVE-2018-8014Critical· 9.8The 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
CVE-2018-1304Medium· 5.9The 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 constr…
CVE-2018-1305Medium· 6.5Security 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
CVE-2016-0706Medium· 4.3Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 does not place org.apache.catalina.manager.StatusManagerServlet on the org/apache/catalina/core/RestrictedServlets.properties list, which allo…
CVE-2016-0714High· 8.8The session-persistence implementation in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 mishandles session attributes, which allows remote authenticated users to bypass intended SecurityMa…