Boolean-Based Blind SQLi
What you'll learn: How attackers extract database information one bit at a time by crafting SQL conditions that change application behavior based on true or false results.
The Core Idea
In Boolean-Based Blind SQL Injection, you can't see direct error messages or query results—but you can observe whether the application behaves differently when your injected SQL condition is true versus false. It's like playing "20 Questions" with a database: you ask yes-or-no questions and deduce the answer from how the application responds.
How It Works
Imagine a vulnerable login page that accepts:
username=admin' AND 1=1-- -
If the page loads normally (true condition), you know injection works. Now try:
username=admin' AND 1=2-- -
If the page behaves differently (false condition), you've confirmed Boolean-based blind SQLi.
Extracting Data Bit by Bit
Attackers use this to extract secrets character-by-character:
username=admin' AND SUBSTRING(password,1,1)='a'-- -
If the page shows normal behavior, the first character is 'a'. If not, try 'b', 'c', etc. Repeat for position 2, 3, 4... until you've extracted the entire password.
You might also test database version:
username=admin' AND (SELECT COUNT(*) FROM users)>10-- -
The application's response (normal vs. error/different page) tells you whether there are more than 10 users.
Why It's Powerful
Even without seeing query results, attackers can map entire databases by observing these behavioral differences—it just takes patience and automation.
Key Takeaway: Boolean-Based Blind SQLi exploits observable application behavior changes (true vs. false responses) to extract sensitive data one piece at a time, making it a slow but effective attack when direct output isn't available.