Skip to content

Apache Tomcat Race Condition vulnerability

Low severity GitHub Reviewed Published Sep 29, 2022 to the GitHub Advisory Database • Updated Mar 11, 2024

Package

maven org.apache.tomcat:tomcat (Maven)

Affected versions

>= 8.5.0, < 8.5.78
>= 9.0.0-M1, < 9.0.62
>= 10.0.0-M1, < 10.0.20
>= 10.1.0-M1, < 10.1.0-M14

Patched versions

8.5.78
9.0.62
10.0.20
10.1.0-M14

Description

The simplified implementation of blocking reads and writes introduced in Tomcat 10 and back-ported to Tomcat 9.0.47 onwards exposed a long standing (but extremely hard to trigger) concurrency bug in Apache Tomcat 10.1.0 to 10.1.0-M12, 10.0.0-M1 to 10.0.18, 9.0.0-M1 to 9.0.60 and 8.5.0 to 8.5.77 that could cause client connections to share an Http11Processor instance resulting in responses, or part responses, to be received by the wrong client.

References

Published by the National Vulnerability Database Sep 28, 2022
Published to the GitHub Advisory Database Sep 29, 2022
Reviewed Sep 30, 2022
Last updated Mar 11, 2024

Severity

Low

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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.203%
(58th percentile)

Weaknesses

CVE ID

CVE-2021-43980

GHSA ID

GHSA-jx7c-7mj5-9438

Source code

Credits

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