[GHSA-hg58-rf2h-6rr7] CometBFT is unstability during blocksync when syncing from malicious peer #4569
+0
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates
Comments
CometBFT experiences instability during block synchronization when syncing from a malicious peer. This issue arises because the malicious peer can disrupt the sync process, causing unexpected behavior and potential security vulnerabilities. Ensuring the reliability of peers and implementing robust verification mechanisms can mitigate this instability, allowing for a more secure and stable block synchronization process in CometBFT.