PricingLoginStart free
Blockchain Smart Contracts with Solidity · Lezione

Vulnerabilità comuni (reentrancy e altre)

Comprenda e mitighi le vulnerabilità più diffuse degli smart contract, come reentrancy, overflow e underflow degli interi e attacchi front-running.

Lezione 1 di 412 passaggi

Vulnerabilità comuni (reentrancy e altre) è una lezione Blockchain Smart Contracts with Solidity gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Blockchain Smart Contracts with Solidity, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Blockchain Smart Contracts with Solidity include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Smart Contract Security: Overview

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.

Understanding Reentrancy Attacks

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.

Reentrancy: A Vulnerable Example

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.

pragma solidity ^0.8.0;

contract VulnerableWithdraw {
  mapping(address => uint) public balances;

  constructor() payable {
    // Fund contract for demo purposes
  }

  function deposit() public payable {
    balances[msg.sender] += msg.value;
  }

  function withdraw(uint _amount) public {
    require(balances[msg.sender] >= _amount, "Insufficient balance");

    // External call FIRST, state update LATER
    (bool success, ) = msg.sender.call{value: _amount}("");
    require(success, "Transfer failed");

    balances[msg.sender] -= _amount; // This line is vulnerable!
  }

  function getBalance() public view returns (uint) {
    return address(this).balance;
  }
}

The Reentrancy Attack Flow

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.

Mitigating Reentrancy: The Fix

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.

Reentrancy: The Fixed Contract

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.

pragma solidity ^0.8.0;

contract SafeWithdraw {
  mapping(address => uint) public balances;

  constructor() payable {
    // Fund contract for demo purposes
  }

  function deposit() public payable {
    balances[msg.sender] += msg.value;
  }

  function withdraw(uint _amount) public {
    // 1. Checks
    require(balances[msg.sender] >= _amount, "Insufficient balance");

    // 2. Effects: Update state BEFORE external call
    balances[msg.sender] -= _amount;

    // 3. Interactions: Make external call LAST
    (bool success, ) = msg.sender.call{value: _amount}("");
    require(success, "Transfer failed");
  }

  function getBalance() public view returns (uint) {
    return address(this).balance;
  }
}

Integer Overflows & Underflows

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).

Overflow/Underflow Example

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.

pragma solidity ^0.8.0;

contract MathVulnerabilities {
  uint8 public smallNumber = 255; // Max for uint8

  function triggerOverflow() public {
    // In Solidity 0.8.0+, this transaction will revert.
    // In older versions, smallNumber would become 0.
    smallNumber = smallNumber + 1;
  }

  function triggerUnderflow() public {
    smallNumber = 0; // Reset for demo
    // In Solidity 0.8.0+, this transaction will revert.
    // In older versions, smallNumber would become 255.
    smallNumber = smallNumber - 1;
  }
}

Front-Running Attacks

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.

Mitigating Front-Running

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.

Vulnerability Check

You've learned about three major smart contract vulnerabilities. Let's test your understanding!

Rispondi nella lezione interattiva

Recap: Security First

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!

Gratis per iniziare

Impara Blockchain Smart Contracts with Solidity con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi
12
Lezioni
48
Inizia a imparare gratisVisualizza il corso completo

Domande Frequenti

La lezione «Vulnerabilità comuni (reentrancy e altre)» è gratuita?

Sì — il testo completo di «Vulnerabilità comuni (reentrancy e altre)» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Blockchain Smart Contracts with Solidity, passa a CoddyKit PRO. Il corso Blockchain Smart Contracts with Solidity include 4 lezioni in totale.

Cosa imparerò in «Vulnerabilità comuni (reentrancy e altre)»?

Comprenda e mitighi le vulnerabilità più diffuse degli smart contract, come reentrancy, overflow e underflow degli interi e attacchi front-running. Eserciti Blockchain Smart Contracts with Solidity con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Blockchain Smart Contracts with Solidity?

Non è richiesta alcuna esperienza precedente. Blockchain Smart Contracts with Solidity su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Vulnerabilità comuni (reentrancy e altre)»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Blockchain Smart Contracts with Solidity?

Sì. Ogni lezione Blockchain Smart Contracts with Solidity include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Vulnerabilità comuni (reentrancy e altre)
  2. Pattern per il controllo degli accessi
  3. Programmazione sicura con SafeMath
  4. Audit, test e bug bounty
← Torna a Blockchain Smart Contracts with Solidity