ช่องโหว่ทั่วไป (การเรียกซ้ำและอื่น ๆ)

Welcome to this crucial lesson on smart contract security! Unlike traditional software, bugs in smart contracts can lead to irreversible loss of funds.

Because contracts on the blockchain are often immutable, fixing vulnerabilities after deployment is incredibly difficult, if not impossible. Security must be a top priority from day one.

Reentrancy is a critical vulnerability where an external call to an untrusted contract can 're-enter' the original contract before the first function call has completed its execution.

This allows the attacker to repeatedly drain funds or manipulate state by calling the vulnerable function multiple times.

Consider this simplified withdrawal contract. Can you spot the potential issue?

The state (balances[msg.sender]) is updated *after* the external call to msg.sender.call. This delay creates a window for attack.

Here's how an attacker exploits the previous contract:

• 1. Deposit: Attacker deposits funds into VulnerableWithdraw.
• 2. Withdraw: Attacker calls withdraw(amount).
• 3. Re-enter: When msg.sender.call transfers Ether to the attacker, their malicious fallback function is triggered.
• 4. Repeat: The fallback function immediately calls withdraw(amount) again, before the original call updates the balance. This repeats until funds are drained.

The most effective way to prevent reentrancy is to follow the Checks-Effects-Interactions (CEI) pattern:

• 1. Checks: Verify all conditions (e.g., require statements).
• 2. Effects: Update all state variables (e.g., balances[msg.sender] -= _amount).
• 3. Interactions: Make external calls (e.g., msg.sender.call).

This ensures state is updated *before* any untrusted external code can execute.

Here's the corrected version of the withdrawal contract, applying the CEI pattern. Notice the order of operations.

Now, the balance is decremented *before* the external call, closing the reentrancy window.

Integer overflows occur when an arithmetic operation results in a value larger than the maximum that the variable type can hold. It 'wraps around' to its minimum value.

Integer underflows are the opposite: when a result is smaller than the minimum value, wrapping around to the maximum.

For example, a uint8 can hold values from 0 to 255. If it's 255 and you add 1, it becomes 0 (overflow). If it's 0 and you subtract 1, it becomes 255 (underflow).

Prior to Solidity 0.8.0, these operations would silently wrap around. Since Solidity 0.8.0, arithmetic operations default to checking for overflows/underflows and will revert if one occurs.

However, understanding the concept is vital, especially when working with older codebases or using unchecked blocks for gas optimization.

Front-running is an attack where a malicious actor observes a pending transaction and submits their own transaction with a higher gas fee to have it executed first.

This is common in DeFi (Decentralized Finance) where transactions like large swaps or liquidations can be anticipated and exploited for profit.

Preventing front-running is challenging due to the public nature of the mempool (pending transaction pool). However, some strategies exist:

• Commit-Reveal Schemes: Users submit a hashed version of their intent (commit), then later reveal the actual data.
• Batching: Grouping transactions together to reduce individual transaction visibility.
• Decentralized Sequencers/L2s: Using solutions that offer more private or controlled transaction ordering.
• Slippage Control: Users setting maximum acceptable price slippage for swaps.

In this lesson, we explored critical smart contract vulnerabilities: reentrancy, integer overflows/underflows, and front-running.

• We saw how reentrancy exploits external calls and how the Checks-Effects-Interactions pattern provides a robust defense.
• We understood how integer arithmetic can lead to unexpected values and the importance of compiler checks (Solidity 0.8.0+).
• Finally, we discussed front-running and methods like commit-reveal to mitigate it.

Always prioritize security in your smart contract development!