Unauthenticated denial of service via malformed packets
Published Jun 23, 2021 · Updated Aug 4, 2024
Improper input validation in FISCO-BCOS 2.7.2 allows remote attackers to crash a blockchain node via malformed network packets. The node fails to safely decode continuously delivered packets in an invalid format, allowing memory consumption to grow until the process crashes. The attack requires a malicious network peer but no authentication or user interaction, and the documented consequence is service interruption without confidentiality or integrity impact.
Summary
What happened
Improper input validation in FISCO-BCOS 2.7.2 allows remote attackers to crash a blockchain node via malformed network packets. The node fails to safely decode continuously delivered packets in an invalid format, allowing memory consumption to grow until the process crashes. The attack requires a malicious network peer but no authentication or user interaction, and the documented consequence is service interruption without confidentiality or integrity impact.
The record
- CVE
- CVE-2021-35041
- Published
- Jun 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1498
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo