Low impact, since this requires a bit of an admin error, but some functions which could be more secure using the _ensureZeroAddress() currently do not implement this and could lead to issues.
Using the PrimeLiquidityProvider.sol in scope as acase study.
Below is the implementation of _ensureZeroAddress()
As seen the above is used within protocol as a modifier/function to revert whenever addresses are being passed, this can be seen to be implemented in the setPrime() function and others, but thats not always the case and in some instances addresses are not ensured to not be zero.
Additionally, as a security measure an isContract() function could be added and used to check for instances where the provided addresses must be valid contracts with code.
Make use of _ensureZeroAddress() in all instances where addresses could be passed.
If the isContract() is going to be implemented then the functionality to be added could look something like this:
And then, this could be applied to instances where addreses must have byte code.
