Apache Tomcat up to 7.0.104/8.5.56/9.0.36/10.0.0-M6 WebSocket Frame Multiple Requests infinite loop

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Apache Tomcat up to 7.0.104/8.5.56/9.0.36/10.0.0-M6. Affected by this issue is some unknown functionality of the component WebSocket Frame Handler. The manipulation as part of Multiple Requests leads to infinite loop. This vulnerability is uniquely identified as CVE-2020-13935. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Apache Tomcat up to 7.0.104/8.5.56/9.0.36/10.0.0-M6 (Application Server Software) and classified as problematic. This issue affects some unknown functionality of the component WebSocket Frame Handler. The manipulation as part of a Multiple Requests leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. The summary by CVE is:
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.
The weakness was disclosed 07/14/2020 (Website). It is possible to read the advisory at lists.apache.org. The identification of this vulnerability is CVE-2020-13935 since 06/08/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/15/2020). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-158026 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 7.0.104
- 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
- 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
- 10.0.0-M6
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Infinite loopCWE: CWE-835 / CWE-404
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/08/2020 🔍07/14/2020 🔍
07/15/2020 🔍
10/30/2020 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-13935 (🔍)
GCVE (CVE): GCVE-0-2020-13935
GCVE (VulDB): GCVE-100-158027
See also: 🔍
Entry
Created: 07/15/2020 14:37Updated: 10/30/2020 13:38
Changes: 07/15/2020 14:37 (40), 07/15/2020 14:42 (18), 10/30/2020 13:38 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.