CVE-2017-12617

When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default servlet to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

CVE-2017-12617 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.1, 8.5.23, 8.0.47, 7.0.82); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2017-12617? CVE-2017-12617 is a high-severity unrestricted upload of dangerous file types vulnerability in org.apache.tomcat:tomcat-catalina (maven), affecting versions >= 9.0.0.M1, <= 9.0.0M27. It is fixed in 9.0.1, 8.5.23, 8.0.47, 7.0.82. The application accepts file uploads without adequately restricting the file type or content.
2. How severe is CVE-2017-12617? CVE-2017-12617 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2017-12617?
   • org.apache.tomcat:tomcat-catalina (maven) (versions >= 9.0.0.M1, <= 9.0.0M27)
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions >= 9.0.0.M1, <= 9.0.0M27)
4. Is there a fix for CVE-2017-12617? Yes. CVE-2017-12617 is fixed in 9.0.1, 8.5.23, 8.0.47, 7.0.82. Upgrade to this version or later.
5. Is CVE-2017-12617 exploitable, and should I be worried? Whether CVE-2017-12617 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-12617 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-12617?
   • Upgrade org.apache.tomcat:tomcat-catalina to 9.0.1 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 8.5.23 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 8.0.47 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 7.0.82 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.1 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 8.5.23 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 8.0.47 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 7.0.82 or later