# CVE-2017-5647: Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat > Attackers can receive responses for wrong requests due to pipelining bugs when send file is enabled, leading to information disclosure. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Apr 2017 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-3gv7-3h64-78cm, UBUNTU-CVE-2017-5647 ## What is CVE-2017-5647? CVE-2017-5647 is a high-severity vulnerability in Apache Tomcat, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2017-5647? 10 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 | 6.0.53 | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 | 6.0.53 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.77 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.77 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.43 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.43 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M19 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M19 | Products: Apache Tomcat. ## How do I fix CVE-2017-5647? Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 6.0.53, 7.0.77, 8.0.43 or 8.5.13. ## Is CVE-2017-5647 being exploited? There is no known exploitation of CVE-2017-5647 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-5647 and fix it if it is affected. What it is: CVE-2017-5647 is a high-severity vulnerability in Apache Tomcat, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-5647 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.53 - org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.53 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.77 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.77 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.43 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.43 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M19 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M19 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-5647/ (Markdown: https://insights.sbomify.com/CVE-2017-5647/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5647 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5647 - OSV: https://osv.dev/vulnerability/CVE-2017-5647 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5647/ Summaries are generated and may contain mistakes; the official description above is the record.