Lack of zero-address validation on address
parameters may lead to transaction reverts, wastes gas, may require resubmission of transactions, and may force contract redeployments in certain cases within the protocol.
There are 11 instances of this issue.
File Link | Instance Count | Instance Link |
---|---|---|
BridgeReth.sol | 1 | 22 |
File Link | Instance Count | Instance Link |
---|---|---|
BridgeSteth.sol | 1 | 24 |
File Link | Instance Count | Instance Links |
---|---|---|
BridgeRouterFacet.sol | 2 | 28,29 |
File Link | Instance Count | Instance Link |
---|---|---|
ExitShortFacet.sol | 1 | 30 |
File Link | Instance Count | Instance Link |
---|---|---|
MarginCallPrimaryFacet.sol | 1 | 30 |
File Link | Instance Count | Instance Link |
---|---|---|
ShortRecordFacet.sol | 1 | 26 |
File Link | Instance Count | Instance Link |
---|---|---|
VaultFacet.sol | 1 | 27 |
File Link | Instance Count | Instance Link |
---|---|---|
YieldFacet.sol | 1 | 31 |
File Link | Instance Count | Instance Link |
---|---|---|
Asset.sol | 1 | 14 |
File Link | Instance Count | Instance Link |
---|---|---|
Ditto.sol | 1 | 16 |
Potential for transaction reverts, wasting of gas, requiring resubmission of transactions, and may force contract redeployments in certain cases.
baudit: a custom static code analysis tool; manual review
Consider adding explicit zero-address validation prior to assignment of a value to an address
state variable.
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.