Skip to content

Expected Behavior Violation in Apache Tomcat

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Apr 18, 2024

Package

maven org.apache.tomcat.embed:tomcat-embed-core (Maven)

Affected versions

>= 9.0.0.M1, <= 9.0.0.M18
>= 8.5.0, <= 8.5.12

Patched versions

9.0.0.M19
8.5.13
maven org.apache.tomcat:tomcat-coyote (Maven)
>= 9.0.0.M1, <= 9.0.0.M18
>= 8.5.0, <= 8.5.12
9.0.0.M19
8.5.13

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.

References

Published by the National Vulnerability Database Apr 17, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 1, 2022
Last updated Apr 18, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.270%
(68th percentile)

Weaknesses

CVE ID

CVE-2017-5651

GHSA ID

GHSA-9hg2-395j-83rm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.