In the function GlobalConfigurationBranch, we use upper and lower bounds, but we could have
Out-of-Bounds Access
If upperBound exceeds the length of globalConfiguration::accountsIdsWithActivePositions, it will result in out-of-bounds access, which will cause the function to revert. There should be checks to ensure upperBound is within the valid range.
Empty Range Handling
If upperBound is less than lowerBound, the function will create an array of negative size (which is not possible) or an array with unexpected size. A check should be added to handle this scenario appropriately.
In the function GlobalConfigurationBranch, failing to check the range of the bound could lead to a revert
failed view transaction
manual
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.