{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-35041 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-35041 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-35041 is a high-severity denial of service vulnerability in n/a, published on 23 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-35041 and fix it if it is affected.\n\nWhat it is: CVE-2021-35041 is a high-severity denial of service vulnerability in n/a, published on 23 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-35041 in the wild and no public exploit code.\n\nAffected product: n/a. 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-35041/ (Markdown: https://insights.sbomify.com/CVE-2021-35041/index.md)","id":"CVE-2021-35041","markdown":"https://insights.sbomify.com/CVE-2021-35041/index.md","name":"CVE-2021-35041","record":{"aliases":["GHSA-5vvg-7wfp-qh9p"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Blockchain node","requires_auth":"none","summary":"A malicious node can crash the FISCO-BCOS blockchain node by sending continuously malformed packets, causing memory exhaustion and service disruption.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fisco-bcos","vendor":"fisco-bcos"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The blockchain node in FISCO-BCOS V2.7.2 may have a bug when dealing with unformatted packet and lead to a crash. A malicious node can send a packet continuously. The packet is in an incorrect format and cannot be decoded by the node correctly. As a result, the node may consume the memory sustainably and crash. More details are shown at: https://github.com/FISCO-BCOS/FISCO-BCOS/issues/1951","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":"Denial of service in n/a","id":"CVE-2021-35041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SQL Injection in Django","id":"CVE-2021-35042"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2021-35039"},"products":["n/a"],"published":"2021-06-23","related":[{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2022-28936","kev_date_added":null,"published":"2022-05-15"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-28937","kev_date_added":null,"published":"2022-05-15"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-26534","kev_date_added":null,"published":"2022-03-16"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2021-46359","kev_date_added":null,"published":"2022-02-07"},{"cvss_score":4,"headline":"Race condition in FISCO-BCOS","id":"CVE-2024-58131","kev_date_added":null,"published":"2025-04-06"}],"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-04","vendors":["n/a"]},"summary":"A malicious node can crash the FISCO-BCOS blockchain node by sending continuously malformed packets, causing memory exhaustion and service disruption.","url":"https://insights.sbomify.com/CVE-2021-35041/"}