Hyperledger Besu up to 1.5.0 HTTP JSON-RPC API Service resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Hyperledger Besu up to 1.5.0. The affected element is an unknown function of the component HTTP JSON-RPC API Service. The manipulation results in resource consumption. This vulnerability is known as CVE-2021-21369. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in Hyperledger Besu up to 1.5.0. It has been classified as problematic. Affected is an unknown part of the component HTTP JSON-RPC API Service. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability.
The weakness was published 03/10/2021. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2021-21369. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 1.5.1 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/hyperledger/besu/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Besu 1.5.1
Patch: github.com
Timeline
12/22/2020 🔍03/10/2021 🔍
03/10/2021 🔍
03/29/2021 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-21369 (🔍)
GCVE (CVE): GCVE-0-2021-21369
GCVE (VulDB): GCVE-100-170880
Entry
Created: 03/10/2021 09:52Updated: 03/29/2021 15:56
Changes: 03/10/2021 09:52 (39), 03/29/2021 15:52 (6), 03/29/2021 15:56 (8)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.