# CVE-2017-5651: Expected Behavior Violation in Apache Tomcat > A race condition in Apache Tomcat's send file processing can cause response mix-ups, potentially leaking data or causing service errors. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **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-9hg2-395j-83rm ## What is CVE-2017-5651? CVE-2017-5651 is a critical 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 In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors introduced a regression in the send file processing. If the send file processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This could result in the same Processor being used for multiple requests which in turn could lead to unexpected errors and/or response mix-up. ## Which versions are affected by CVE-2017-5651? 8 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core and org.apache.tomcat:tomcat-coyote. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.0.M19 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.0.M19 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0.M1 | 9.0.0.M19 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0.M1 | 9.0.0.M19 | Products: Apache Tomcat. ## How do I fix CVE-2017-5651? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 8.5.13 or 9.0.0.M19. ## Is CVE-2017-5651 being exploited? There is no known exploitation of CVE-2017-5651 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-5651 and fix it if it is affected. What it is: CVE-2017-5651 is a critical 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-5651 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M19 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M19 - org.apache.tomcat:tomcat-coyote (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat:tomcat-coyote (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat:tomcat-coyote (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M19 - org.apache.tomcat:tomcat-coyote (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-5651/ (Markdown: https://insights.sbomify.com/CVE-2017-5651/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5651 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5651 - OSV: https://osv.dev/vulnerability/CVE-2017-5651 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5651/ Summaries are generated and may contain mistakes; the official description above is the record.