code-423n4 / 2023-10-brahma-findings

8 stars 7 forks source link

`ExecutorPlugin` is not enabled as module, when `subaccounts` are created. #373

Closed c4-submissions closed 10 months ago

c4-submissions commented 11 months ago

Lines of code

https://github.com/code-423n4/2023-10-brahma/blob/dd0b41031b199a0aa214e50758943712f9f574a0/contracts/src/core/SafeDeployer.sol#L168-L205

Vulnerability details

According to the Contest Overview,

Impact

This leads to a situation where subaccounts are created but lack ExecutorPlugin set as a module, this prevents executors from executing transactions as a module.

Tools Used

Manual Review

Recommended Mitigation Steps

A call to set ExecutorPlugin as a module should be added to the _setupSubAccount() function to ensure that every new subaccount has ExecutorPlugin enabled.

Assessed type

Access Control

c4-pre-sort commented 11 months ago

raymondfam marked the issue as low quality report

c4-pre-sort commented 11 months ago

raymondfam marked the issue as primary issue

raymondfam commented 11 months ago

Intended design. Insufficient proof.

alex-ppg commented 10 months ago

The ExecutorPlugin is not meant to be activated by default for sub-accounts; it is meant to be activated at will after deployment.

As such, this exhibit is invalid as it details intended design.

c4-judge commented 10 months ago

alex-ppg marked the issue as unsatisfactory: Invalid