Vulnerabilities for Blockchain and Web3 Developers
Smart contract vulnerabilities are coding and design flaws that let attackers drain or lock funds. Common classes include reentrancy, missing access control, integer and rounding errors, oracle and price manipulation, front-running, and unsafe delegatecall or upgrade logic. Because deployed code is public and transactions are final, these bugs are costly.
Stage: Security · Part of the Blockchain and Web3 Developer roadmap · Last reviewed 19 November 2026
What to learn in Vulnerabilities
- Exploit and then fix a reentrancy bug using checks-effects-interactions
- Spot missing access control on an initialiser or admin function
- Explain how flash loans enable price oracle manipulation
- Describe front-running and how commit-reveal reduces it
- Identify rounding errors in share and vault accounting
Vulnerabilities interview questions
What is a reentrancy attack and how do you prevent it?
Reentrancy happens when a contract sends funds to an external address before updating its own state, letting the callee call back and withdraw again. Prevent it by updating state first, then interacting, and by adding a reentrancy guard on sensitive functions.
Why is using spot price from a DEX pool as an oracle dangerous?
A spot price can be moved inside one transaction using a flash loan, so a contract reading it can be tricked into mispricing collateral or rewards. Safer options are time-weighted average prices or decentralised oracle feeds with sanity checks.
Where Vulnerabilities fits in the Blockchain and Web3 Developer roadmap
Vulnerabilities belongs to the Security stage (intermediate level), which takes about 5 hours. The core discipline.
Other units in this stage
Back to the full Blockchain and Web3 Developer roadmap