Closed c4-submissions closed 1 year ago
raymondfam marked the issue as low quality report
raymondfam marked the issue as duplicate of #39
alex-ppg marked the issue as not a duplicate
This is a deliberate Brahma decision; even if the executor does not match the msg.sender
, the signed payload provided in the transaction must be signed by the executor.
As the executor as well as the policy validator have authorized the transaction, there is no readily apparent vulnerability from permitting anyone to submit these payloads for execution.
alex-ppg marked the issue as unsatisfactory: Invalid
Lines of code
https://github.com/code-423n4/2023-10-brahma/blob/a6424230052fc47c4215200c19a8eef9b07dfccc/contracts/src/core/ExecutorPlugin.sol#L112
Vulnerability details
Impact
the function _validateExecutionRequest checks the valid excutor account by the address of account given in call data instead of msg.sender which is realy easily exploitable
if you look at the function
it checks the address of executor with given account address which must be msg.sender otherwise has 0 impact
Proof of Concept
Tools Used
vscode
Recommended Mitigation Steps
Assessed type
Invalid Validation