The extraArgs parameter used in the WrappedTokenBridge::_buildCCIPMessage function should be mutable in order to allow compatibility with future CCIP upgrade.
The parameter extraArgs helps to specify the gasLimit, in the other hand if there is a transfer of tokens directly to an EOA the value can be zero.
The problem is that inside the function WrappedTokenBridge::_buildCCIPMessage an immutable extraArgs is used (code line 223), which can be harmful since in order to have compatibility with CCIP updates it is necessary for extraArgs to be mutable.
According to CCIP documentation:
The purpose of extraArgs is to allow compatibility with future CCIP upgrades. To get this benefit, make sure that extraArgs is mutable in production deployments.
Compatibility problems may exist in CCIP updates if extraArgs remains immutable.
Manual review
Add appropriate modifications to be able to change extraArgs if necessary.
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.