CVE-2017-5647

A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, 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.

CVE-2017-5647 has a CVSS score of 7.5 (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.0.M19, 8.5.13, 7.0.77, 6.0.53, 8.0.43); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2017-5647? CVE-2017-5647 is a high-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 9.0.0.M1, <= 9.0.0.M18. It is fixed in 9.0.0.M19, 8.5.13, 7.0.77, 6.0.53, 8.0.43.
2. How severe is CVE-2017-5647? CVE-2017-5647 has a CVSS score of 7.5 (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 versions of org.apache.tomcat:tomcat are affected by CVE-2017-5647? org.apache.tomcat:tomcat (maven) versions >= 9.0.0.M1, <= 9.0.0.M18 is affected.
4. Is there a fix for CVE-2017-5647? Yes. CVE-2017-5647 is fixed in 9.0.0.M19, 8.5.13, 7.0.77, 6.0.53, 8.0.43. Upgrade to this version or later.
5. Is CVE-2017-5647 exploitable, and should I be worried? Whether CVE-2017-5647 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-5647 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-5647?
   • Upgrade org.apache.tomcat:tomcat to 9.0.0.M19 or later
   • Upgrade org.apache.tomcat:tomcat to 8.5.13 or later
   • Upgrade org.apache.tomcat:tomcat to 7.0.77 or later
   • Upgrade org.apache.tomcat:tomcat to 6.0.53 or later
   • Upgrade org.apache.tomcat:tomcat to 8.0.43 or later