fix: apply CEI pattern in DisputeGameFactory create() and createWithInitData()#366
Open
dev-khimesh wants to merge 1 commit into
Open
fix: apply CEI pattern in DisputeGameFactory create() and createWithInitData()#366dev-khimesh wants to merge 1 commit into
dev-khimesh wants to merge 1 commit into
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes a Checks-Effects-Interactions (CEI) violation in
DisputeGameFactory.solidentified by Lumi Security Audit (Issue #356).Vulnerability
Both
create()andcreateWithInitData()perform an external call (proxy_.initialize()/proxy_.initializeWithInitData()) before updating the factory's internal state via_finalizeGameCreation(). This violates the CEI pattern and exposes the contract to:initializefunction could re-enter the factory before the game is registered_disputeGamesmapping hasn't been updated yetFix
Swapped the order so
_finalizeGameCreation(state effect) runs beforeproxy_.initialize()(external interaction). The EVM auto-rolls back state if the subsequent call reverts, preserving safety.Severity: Medium
Closes #356