An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function sweep(address _token, uint _amount) returns (bool) { start = 0x123456789; return true;} }. Then, when one calls the function sweep() in the UserWallet contract, it will change the sweeperList to 0X123456789.
References
Link | Resource |
---|---|
https://github.com/hellowuzekai/blockchains/blob/master/delegatecall.md | Exploit Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2022-10-03T16:22:29
Updated: 2022-10-03T16:22:29
Reserved: 2022-10-03T00:00:00
Link: CVE-2018-14085
JSON object: View
NVD Information
Status : Analyzed
Published: 2018-07-16T02:29:00.317
Modified: 2018-09-12T14:19:12.603
Link: CVE-2018-14085
JSON object: View
Redhat Information
No data.
CWE