First published: Tue Mar 09 2021(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Hyperledger Besu | <1.5.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-21369 is classified as medium due to its potential denial-of-service impact.
To fix CVE-2021-21369, upgrade Hyperledger Besu to version 1.5.1 or later.
CVE-2021-21369 affects all versions of Hyperledger Besu prior to 1.5.1.
CVE-2021-21369 involves a denial-of-service attack that exploits the HTTP JSON-RPC API service.
Yes, the vulnerability can be exploited if username and password authentication is enabled for the HTTP JSON-RPC API service.