FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed when a malicious node (that has modified the codebase to allow a large min_seal_time value) joins a blockchain network.
The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.
The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.
Link | Tags |
---|---|
https://github.com/FISCO-BCOS/FISCO-BCOS/issues/4656 | issue tracking exploit |