Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2017-5647

HIGH

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Also known asGHSA-3gv7-3h64-78cm
Published
Apr 17, 2017
Updated
Apr 16, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
16.8%probability of exploitation in next 30 days
Moderate Risk97th percentile+14.56%
0.00%7.19%14.4%21.6%1.1%16.8%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat9.0.0.M1&&< 9.0.0.M199.0.0.M19
Mavenorg.apache.tomcat:tomcat8.5.0&&< 8.5.138.5.13
Mavenorg.apache.tomcat:tomcat8.0.0&&< 8.0.438.0.43
Mavenorg.apache.tomcat:tomcat7.0.0&&< 7.0.777.0.77
Mavenorg.apache.tomcat:tomcat6.0.0&&< 6.0.536.0.53

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.tomcat:tomcat to 9.0.0.M19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5647 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2017-5647 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-5647. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2017-5647 in your dependencies?

O3 detects CVE-2017-5647 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.