Transaction hang via peer-controlled sealing delay
Published Apr 6, 2025 · Updated Apr 7, 2025
Incorrect transaction-pool synchronization in FISCO BCOS 3.11.0 allows remote attackers to hang blockchain transactions through a malicious node. The PBFT transaction flow accepts a peer node's excessive min_seal_time value as the network-wide sealing delay instead of enforcing a chain-agreed limit. The attacker must join the permissioned network with a modified node; an extreme value prevents legitimate transactions from returning execution results.
Summary
What happened
Incorrect transaction-pool synchronization in FISCO BCOS 3.11.0 allows remote attackers to hang blockchain transactions through a malicious node. The PBFT transaction flow accepts a peer node's excessive min_seal_time value as the network-wide sealing delay instead of enforcing a chain-agreed limit. The attacker must join the permissioned network with a modified node; an extreme value prevents legitimate transactions from returning execution results.
The record
- CVE
- CVE-2024-58131
- Published
- Apr 6, 2025
- Updated
- Apr 7, 2025
- Vendor
- Financial Services Blockchain Consortium (Shenzhen)
- Product
- FISCO BCOS
- Classifications
- CWE-821, CWE-662, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2025CVE publishedPublication date reported by the CVE source.
- Apr 7, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Four-node min_seal_time transaction-hang reproductionproof of concept · demonstrated
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