SWC-112

Title

Relationships

Description

There exists a special variant of a message call, named delegatecall which is identical to a message call apart from the fact that the code at the target address is executed in the context of the calling contract and msg.sender and msg.value do not change their values. This allows a smart contract to dynamically load code from a different address at runtime. Storage, current address and balance still refer to the calling contract.

Calling into untrusted contracts is very dangerous, as the code at the target address can change any storage values of the caller and has full control over the caller's balance.

Remediation

Use delegatecall with caution and make sure to never call into untrusted contracts. If the target address is derived from user input ensure to check it against a whitelist of trusted contracts.

proxy_fixed.yaml

proxy_pattern_false_positive.sol

pragma solidity ^0.4.24;
contractproxy{
address owner;
functionproxyCall(address _to, bytes _data) external{
require( !_to.delegatecall(_data));
}
functionwithdraw() external{
require(msg.sender == owner);
msg.sender.transfer(address(this).balance);
}
}
/*
You can't use proxyCall to change the owner address as either:
1) the delegatecall reverts and thus does not change owner
2) the delegatecall does not revert and therefore will cause the proxyCall to revert and preventing owner from changing
This false positive may seem like a really edge case, however since you can revert data back to proxy this patern is useful for proxy architectures
*/