GHSA-9hg2-395j-83rm CVE-2017-5651

Expected Behavior Violation in Apache Tomcat

Critical Maven

Severity: 9.8 / 10; Critical · CVSS 3.0
Exploit chance (EPSS): 7.75%; Chance of exploitation in the next 30 days. Higher than 94.64% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-440 Expected Behavior Violation
Fix: Available; 2 packages have a fixed version

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.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.apache.tomcat.embed:tomcat-embed-core	`>= 9.0.0.M1, < 9.0.0.M19`	`9.0.0.M19`
org.apache.tomcat.embed:tomcat-embed-core	`>= 8.5.0, < 8.5.13`	`8.5.13`
org.apache.tomcat:tomcat-coyote	`>= 9.0.0.M1, < 9.0.0.M19`	`9.0.0.M19`
org.apache.tomcat:tomcat-coyote	`>= 8.5.0, < 8.5.13`	`8.5.13`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.tomcat.embed:tomcat-embed-core Maven → `9.0.0.M19`

maven

<dependency><groupId>org.apache.tomcat.embed</groupId><artifactId>tomcat-embed-core</artifactId><version>9.0.0.M19</version></dependency>

gradle

implementation("org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19")

org.apache.tomcat:tomcat-coyote Maven → `9.0.0.M19`

maven

<dependency><groupId>org.apache.tomcat</groupId><artifactId>tomcat-coyote</artifactId><version>9.0.0.M19</version></dependency>

gradle

implementation("org.apache.tomcat:tomcat-coyote:9.0.0.M19")

Severity breakdown

CVSS 3.0 9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-440: Expected Behavior Violation

A feature, API, or function does not perform according to its specification.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2017-5651

Packages

github.com/apache/tomcat

Timeline

May 13, 2022 Published
Apr 18, 2024 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-83qj-6fr2-vhqg Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUT	Critical Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-qppj-fm5r-hxr3 HTTP/2 Stream Cancellation Attack	Medium Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-xjgh-84hx-56c5 Unrestricted Upload of File with Dangerous Type Apache Tomcat	High Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
CVE-2020-1938 Improper Privilege Management in Tomcat	Critical Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-pjfr-qf3p-3q25 When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server	High Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-h3x4-894j-xpx5 Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-9xv2-5v5q-p794 Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-f525-44xv-f2qj Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor