Apache Tomcat up to 8.5.77/9.0.60/10.0.18/10.1.0-M12 Client Connection race condition

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Apache Tomcat up to 8.5.77/9.0.60/10.0.18/10.1.0-M12. The impacted element is an unknown function of the component Client Connection Handler. This manipulation causes race condition. The identification of this vulnerability is CVE-2021-43980. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Apache Tomcat up to 8.5.77/9.0.60/10.0.18/10.1.0-M12 (Application Server Software). It has been declared as problematic. Affected by this vulnerability is an unknown code of the component Client Connection Handler. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was shared 09/28/2022. The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2021-43980 since 11/17/2021. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 8.5.0
- 8.5.1
- 8.5.2
- 8.5.3
- 8.5.4
- 8.5.5
- 8.5.6
- 8.5.7
- 8.5.8
- 8.5.9
- 8.5.10
- 8.5.11
- 8.5.12
- 8.5.13
- 8.5.14
- 8.5.15
- 8.5.16
- 8.5.17
- 8.5.18
- 8.5.19
- 8.5.20
- 8.5.21
- 8.5.22
- 8.5.23
- 8.5.24
- 8.5.25
- 8.5.26
- 8.5.27
- 8.5.28
- 8.5.29
- 8.5.30
- 8.5.31
- 8.5.32
- 8.5.33
- 8.5.34
- 8.5.35
- 8.5.36
- 8.5.37
- 8.5.38
- 8.5.39
- 8.5.40
- 8.5.41
- 8.5.42
- 8.5.43
- 8.5.44
- 8.5.45
- 8.5.46
- 8.5.47
- 8.5.48
- 8.5.49
- 8.5.50
- 8.5.51
- 8.5.52
- 8.5.53
- 8.5.54
- 8.5.55
- 8.5.56
- 8.5.57
- 8.5.58
- 8.5.59
- 8.5.60
- 8.5.61
- 8.5.62
- 8.5.63
- 8.5.64
- 8.5.65
- 8.5.66
- 8.5.67
- 8.5.68
- 8.5.69
- 8.5.70
- 8.5.71
- 8.5.72
- 8.5.73
- 8.5.74
- 8.5.75
- 8.5.76
- 8.5.77
- 9.0.0
- 9.0.1
- 9.0.2
- 9.0.3
- 9.0.4
- 9.0.5
- 9.0.6
- 9.0.7
- 9.0.8
- 9.0.9
- 9.0.10
- 9.0.11
- 9.0.12
- 9.0.13
- 9.0.14
- 9.0.15
- 9.0.16
- 9.0.17
- 9.0.18
- 9.0.19
- 9.0.20
- 9.0.21
- 9.0.22
- 9.0.23
- 9.0.24
- 9.0.25
- 9.0.26
- 9.0.27
- 9.0.28
- 9.0.29
- 9.0.30
- 9.0.31
- 9.0.32
- 9.0.33
- 9.0.34
- 9.0.35
- 9.0.36
- 9.0.37
- 9.0.38
- 9.0.39
- 9.0.40
- 9.0.41
- 9.0.42
- 9.0.43
- 9.0.44
- 9.0.45
- 9.0.46
- 9.0.47
- 9.0.48
- 9.0.49
- 9.0.50
- 9.0.51
- 9.0.52
- 9.0.53
- 9.0.54
- 9.0.55
- 9.0.56
- 9.0.57
- 9.0.58
- 9.0.59
- 9.0.60
- 10.0.0
- 10.0.1
- 10.0.2
- 10.0.3
- 10.0.4
- 10.0.5
- 10.0.6
- 10.0.7
- 10.0.8
- 10.0.9
- 10.0.10
- 10.0.11
- 10.0.12
- 10.0.13
- 10.0.14
- 10.0.15
- 10.0.16
- 10.0.17
- 10.0.18
- 10.1.0-M12
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.1
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.7
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
11/17/2021 🔍09/28/2022 🔍
09/28/2022 🔍
10/24/2022 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Status: Confirmed
CVE: CVE-2021-43980 (🔍)
GCVE (CVE): GCVE-0-2021-43980
GCVE (VulDB): GCVE-100-209689
Entry
Created: 09/28/2022 19:17Updated: 10/24/2022 19:33
Changes: 09/28/2022 19:17 (40), 10/24/2022 19:33 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.