This repo contains all the details to follow along with the "All things reentrancy" workshop/talk. Check the YT recording of the live session with the Calyptus community here.
⭐ The target audience includes both smart contract developers looking to improve their secure coding practices and beginner auditors/security people looking to get an overview on how to identify basic examples of the wider family of reentrancy bugs and crafting your first exploit/proof of concept for each of them.
👉 If you are already a little bit ahead on your Solidity security journey, this content may be too basic for you 😃
All the exploitation tests aka Proof of Concept (PoC) will be done using foundry. It does not matter if you are not familiar with the tool as we will use just a fraction of its capabilities for testing basic scenarios and the test cases, written in solidity, are provided as part of the exercise so participants can just focus on the attacker contracts.
First and foremost, install Foundry following these details. After the successful installation, please run the following to check that everything is in place:
foundryup # look for updates
forge init myTestProject # Create a foundry template project
cd myTestProject
forge test # run the current testsIf the above tests were successful, your Foundry instance is ready for the workshop ✔️
First and foremost, clone this repo, cd into the dir and install the following dependencies:
# Download the latest version of the Foundry std library under /lib
forge install foundry-rs/forge-std
# Download the latest version of the OZ contracts under /lib
forge install openzeppelin/openzeppelin-contracts
# List current remappings, which should already include the above
forge remappings This is enough for foundry to recognize the mappings and successfully compile but let’s add one more thing so VS code stops showing the import error
forge remappings > remappings.txtYou will find one vulnerable contract for each type of reentrancy bug currently covered. Each of them will have a template attacker contract named 0X-template_attacker.sol ready for you to craft your own attacking contract. Finally, under test/0X-poc.sol you will find a test/PoC ready to fire your attacker contract. Proposed solutions can be found in src/solutions/... but not yet 😇
- Basic reentrancy
- Token-callback reentrancy
- Cross-function reentrancy
- Cross-contract reentrancy
- Basic reentrancy subtracting
- Basic reentrancy subtracting - more complex
- Read only reentrancy
This is the most basic type of reentrancy, the victim exposes the following functions:
function withdrawAll() externalfunction withdrawSome() externalfunction deposit() external payablefunction userBalance (address user) public view returns (uint256)
Modify src/00-template_sttacker.sol to successfully pass the test found in test/00-poc.sol to prove the success of your attack. Play around with both withdraw functions to understand why one of them is directly exploitable and not the other! Are you able to showcase an exploit scenario for both cases?
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/00-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!Here we have a basic ERC-721 implementation that exposes just one relevant function:
function mint() external payable
Modify src/01-template_attacker.sol to successfully pass the test found in test/01-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/01-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!The target contract is very similar to example 00, however, the vulnerable function is now marked as nonReentrant. A new feature to move funds has also been added!
function deposit() external payablefunction withdraw() external nonReentrant()function transferTo(address _recipient, uint _amount) external
Modify src/02-template_attacker.sol to successfully pass the test found in test/02-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/02-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!The idea is similar to the previous one, however, instead of book-keeping each deposited eth a stEth ERC-20 token is minted. Also... every function is nonReentrant.
function stake() external payable nonReentrant()function unstake() external nonReentrant()
The auxiliary token contract includes a burnAll() function that allows the burned to burn the whole balance of a given user.
Modify src/03-template_attacker.sol to successfully pass the test found in test/03-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/03-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!This example is a simplified vault, which allows the user with the highest deposit to be flagged as King. It exposes the following functions:
function deposit() external payablefunction withdraw(uint256 amount) externalfunction claimKing() external returns (bool)
Modify src/04_1-template_attacker.sol to successfully pass the test found in test/04_1-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/04_1-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!This example is a simplified implementation of a tokenized vault, which increases the user shares when eth is locked in the contract. It exposes the following functions:
function deposit() external payablefunction withdraw(uint256 amount) externalfunction stake(uint256 amount) external returns (uint256)function unstake(uint256 amount) external returns (uint256)
Modify src/04_2-template_attacker.sol to successfully pass the test found in test/04_2-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/04_2-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!The last one depicts a Liquidity pool ETH-stETH that is used as a data source by a Lending protocol (check src/periphery/reader_lender.sol). Every function is nonReentrant and has external interactions in the last place.
function addLiquidity(uint256 stEth_amount, uint256 eth_amount) external payable nonReentrant() returns (uint256)function removeLiquidity(uint256 lp_amount) external nonReentrant() returns (uint256, uint256)function getSpotPriceStEth(uint256 amount) public view returns (uint256)function getSpotPriceEth(uint256 amount) public view returns (uint256)
Modify src/05-template_attacker.sol to successfully pass the test found in test/05-poc.sol to prove the success of your attack.
💻 Use the following line to run the test and check the success of your proof of concept:
forge test --match-path test/05-poc.sol -vvv # If you add a fourth v (-vvvv) you will see the traces for successful tests too, very interesting!