Skip to content

Apache Tomcat Request and/or response mix-up

Moderate severity GitHub Reviewed Published Nov 18, 2024 to the GitHub Advisory Database • Updated Nov 18, 2024

Package

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

Affected versions

>= 9.0.92, < 9.0.96
>= 10.1.27, < 10.1.31
>= 11.0.0-M23, < 11.0.0

Patched versions

9.0.96
10.1.31
11.0.0
maven org.apache.tomcat:tomcat-coyote (Maven)
>= 9.0.92, < 9.0.96
>= 10.1.27, < 10.1.31
>= 11.0.0-M23, < 11.0.0
9.0.96
10.1.31
11.0.0

Description

Incorrect object re-cycling and re-use vulnerability in Apache Tomcat. Incorrect recycling of the request and response used by HTTP/2 requests could lead to request and/or response mix-up between users.

This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.0-M26, from 10.1.27 through 10.1.30, from 9.0.92 through 9.0.95.

Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fixes the issue.

References

Published by the National Vulnerability Database Nov 18, 2024
Published to the GitHub Advisory Database Nov 18, 2024
Reviewed Nov 18, 2024
Last updated Nov 18, 2024

Severity

Moderate

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
Low
Integrity
Low
Availability
None

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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Weaknesses

CVE ID

CVE-2024-52317

GHSA ID

GHSA-qvf5-hvjx-wm27

Source code

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