The enableBridge
function in the smart contract lacks an event emission when the bridge's enabled status is changed. This omission reduces transparency and makes it difficult for external systems and users to track critical state changes in the bridge's operational status.
The vulnerability is present in the enableBridge
function:
This function changes the operational status of the bridge but fails to emit an event to notify users and external systems of this critical state change.
Users and external systems have no on-chain way to track when the bridge is enabled or disabled.
Manual review
Implement an event emission in the enableBridge
function:
Please, do not suppose impacts, think about the real impact of the bug and check the CodeHawks documentation to confirm: https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity A PoC always helps to understand the real impact possible.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.