Red Hat JBossWeb up to 7.5.31 WebSocket Multiple Requests resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Red Hat JBossWeb up to 7.5.31. The impacted element is an unknown function of the component WebSocket. This manipulation as part of Multiple Requests causes resource consumption. This vulnerability is handled as CVE-2020-14384. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Red Hat JBossWeb up to 7.5.31 (Application Server Software). It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component WebSocket. The manipulation as part of a Multiple Requests leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
A flaw was found in JBossWeb in versions before 7.5.31.Final-redhat-3. The fix for CVE-2020-13935 was incomplete in JBossWeb, leaving it vulnerable to a denial of service attack when sending multiple requests with invalid payload length in a WebSocket frame. The highest threat from this vulnerability is to system availability.
The weakness was released 09/09/2020 as Bug 1875176 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2020-14384 since 06/17/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 7.5.31.Final-redhat-3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 7.5.0
- 7.5.1
- 7.5.2
- 7.5.3
- 7.5.4
- 7.5.5
- 7.5.6
- 7.5.7
- 7.5.8
- 7.5.9
- 7.5.10
- 7.5.11
- 7.5.12
- 7.5.13
- 7.5.14
- 7.5.15
- 7.5.16
- 7.5.17
- 7.5.18
- 7.5.19
- 7.5.20
- 7.5.21
- 7.5.22
- 7.5.23
- 7.5.24
- 7.5.25
- 7.5.26
- 7.5.27
- 7.5.28
- 7.5.29
- 7.5.30
- 7.5.31
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Resource consumptionCWE: CWE-400 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JBossWeb 7.5.31.Final-redhat-3
Timeline
06/17/2020 🔍09/09/2020 🔍
09/09/2020 🔍
09/09/2020 🔍
Sources
Vendor: redhat.comAdvisory: Bug 1875176
Status: Not defined
CVE: CVE-2020-14384 (🔍)
GCVE (CVE): GCVE-0-2020-14384
GCVE (VulDB): GCVE-100-160981
Entry
Created: 09/09/2020 21:05Updated: 09/09/2020 21:10
Changes: 09/09/2020 21:05 (42), 09/09/2020 21:10 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.