{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21369 is a medium-severity denial of service vulnerability in hyperledger besu, published on 9 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21369 and fix it if it is affected.\n\nWhat it is: CVE-2021-21369 is a medium-severity denial of service vulnerability in hyperledger besu, published on 9 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21369 in the wild and no public exploit code.\n\nAffected product: hyperledger besu. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-21369/ (Markdown: https://insights.sbomify.com/CVE-2021-21369/index.md)","id":"CVE-2021-21369","markdown":"https://insights.sbomify.com/CVE-2021-21369/index.md","name":"CVE-2021-21369","record":{"aliases":["GHSA-qgfj-mjpc-7w3q"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Ethereum client","requires_auth":"low_privilege","summary":"An attacker can cause denial of service in Hyperledger Besu by overloading the login endpoint with invalid credentials when authentication is enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"besu","vendor":"linuxfoundation"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Potential DoS in Besu HTTP JSON-RPC API","id":"CVE-2021-21369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-Site Scripting in Content Preview (CType menu)","id":"CVE-2021-21370"},"packages":[],"prev":{"headline":"Prototype poisoning","id":"CVE-2021-21368"},"products":["besu"],"published":"2021-03-09","related":[{"cvss_score":9.1,"headline":"Incorrect Conversion between Numeric Types in Besu Ethereum Client","id":"CVE-2022-36025","kev_date_added":null,"published":"2022-09-24"},{"cvss_score":7.5,"headline":"SHL, SHR, and SAR operations trigger native exception at key values in besu","id":"CVE-2021-41272","kev_date_added":null,"published":"2021-12-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["hyperledger"]},"summary":"An attacker can cause denial of service in Hyperledger Besu by overloading the login endpoint with invalid credentials when authentication is enabled.","url":"https://insights.sbomify.com/CVE-2021-21369/"}