Closed Aboudjem closed 3 months ago
This comment was automatically generated by the GitHub Actions workflow.
Generated at commit: 07c012a965078a3e22922aaf032d37609307c694, compared to commit: 5a75c21571a1cca8431b5c7b1cd1737e8f0ca367
Contract | Method | Avg (+/-) | % |
---|
Attention: Patch coverage is 74.41860%
with 11 lines
in your changes missing coverage. Please review.
Please upload report for BASE (
fix/security-m01@5a75c21
). Learn more about missing BASE report.
Files | Patch % | Lines |
---|---|---|
contracts/base/ModuleManager.sol | 75.00% | 5 Missing :warning: |
contracts/Nexus.sol | 76.47% | 4 Missing :warning: |
contracts/base/BaseAccount.sol | 0.00% | 2 Missing :warning: |
@Aboudjem
what is done specific to this?
Fix: Implement proper authorization control to ensure only authorized entities can invoke it
I don't see changes related to it. we also discussed fallback handler should implement it's own auth control and we are gonna make changes on the EIP PR. cc @filmakarov
can you close this PR and redo it if only there are additional test cases. bunch of linting makes it very hard to review..
Should this be a remediation for this https://codehawks.cyfrin.io/c/2024-07-biconomy/s/179 ?
Should this be a remediation for this https://codehawks.cyfrin.io/c/2024-07-biconomy/s/179 ?
No, anyone should be able to invoke fallback handlers. the actual access control (if required) should be implemented in the handlers themselves..
@Aboudjem
what is done specific to this?
Fix: Implement proper authorization control to ensure only authorized entities can invoke it
I don't see changes related to it. we also discussed fallback handler should implement it's own auth control and we are gonna make changes on the EIP PR. cc @filmakarov
can you close this PR and redo it if only there are additional test cases. bunch of linting makes it very hard to review..
Implement proper authorization control in the fallback function to ensure that only authorized entities can invoke it. This can be achieved by adding a modifier to check the sender's authorization before routing the call to the fallback handler. The existing onlyEntryPointOrSelf modifier could be used or an new modifier also including executorModuls might be appropriate.
At this point, the entrypoint and the onlyEntrypoint or onlySelfOrEntrypoint are not visible, any suggestion?
Yes my husky script messed a bit with the linter
@Aboudjem what is done specific to this?
Fix: Implement proper authorization control to ensure only authorized entities can invoke it
I don't see changes related to it. we also discussed fallback handler should implement it's own auth control and we are gonna make changes on the EIP PR. cc @filmakarov can you close this PR and redo it if only there are additional test cases. bunch of linting makes it very hard to review..
Implement proper authorization control in the fallback function to ensure that only authorized entities can invoke it. This can be achieved by adding a modifier to check the sender's authorization before routing the call to the fallback handler. The existing onlyEntryPointOrSelf modifier could be used or an new modifier also including executorModuls might be appropriate.
At this point, the entrypoint and the onlyEntrypoint or onlySelfOrEntrypoint are not visible, any suggestion?
Yes my husky script messed a bit with the linter
dont think any of this change makes sense.
@Aboudjem what is done specific to this?
Fix: Implement proper authorization control to ensure only authorized entities can invoke it
I don't see changes related to it. we also discussed fallback handler should implement it's own auth control and we are gonna make changes on the EIP PR. cc @filmakarov can you close this PR and redo it if only there are additional test cases. bunch of linting makes it very hard to review..
Implement proper authorization control in the fallback function to ensure that only authorized entities can invoke it. This can be achieved by adding a modifier to check the sender's authorization before routing the call to the fallback handler. The existing onlyEntryPointOrSelf modifier could be used or an new modifier also including executorModuls might be appropriate.
At this point, the entrypoint and the onlyEntrypoint or onlySelfOrEntrypoint are not visible, any suggestion? Yes my husky script messed a bit with the linterdont think any of this change makes sense.
then close the PR
M-03. Anyone can call the fallbackFunction because of missing authorization control
fallback
function inModuleManager
.