CVE-2021-21369
Summary
| CVE | CVE-2021-21369 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-03-09 18:15:00 UTC |
| Updated | 2021-03-16 17:25:00 UTC |
| Description | Hyperledger Besu is an open-source, MainNet compatible, Ethereum client written in Java. In Besu before version 1.5.1 there is a denial-of-service vulnerability involving the HTTP JSON-RPC API service. If username and password authentication is enabled for the HTTP JSON-RPC API service, then prior to making any requests to an API endpoint the requestor must use the login endpoint to obtain a JSON web token (JWT) using their credentials. A single user can readily overload the login endpoint with invalid requests (incorrect password). As the supplied password is checked for validity on the main vertx event loop and takes a relatively long time this can cause the processing of other valid requests to fail. A valid username is required for this vulnerability to be exposed. This has been fixed in version 1.5.1. |
Risk And Classification
Problem Types: CWE-400
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Linuxfoundation | Besu | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Potential DoS in Besu HTTP JSON-RPC API · Advisory · hyperledger/besu · GitHub | CONFIRM | github.com | Third Party Advisory |
| Improvements to authenticated JSON-RPC permissions checking (#1144) · hyperledger/besu@06e35a5 · GitHub | MISC | github.com | Patch, Third Party Advisory |
| Improvements to authenticated JSON-RPC permissions checking by macfarla · Pull Request #1144 · hyperledger/besu · GitHub | MISC | github.com | Patch, Third Party Advisory |
| besu/CHANGELOG.md at master · hyperledger/besu · GitHub | MISC | github.com | Release Notes, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.