What type of SQL injection attack modifies a database without revealing the results to the attacker?

Question

Options

• ABlind SQL injection
• BError-based SQL injection
• CUnion-based SQL injection
• DSecond-order SQL injection

• A
  76% (26)
• B
  15% (5)
• C
  3% (1)
• D
  6% (2)

Explanation

Blind SQL injection fits here because the attacker injects malicious SQL that modifies or queries the database, but receives no direct output - they infer results through side effects like timing delays (SLEEP()) or boolean-based behavior changes (page loads differently when true vs. false). The word "blind" captures the key idea: the attacker is flying without visibility into query results.

Why the distractors are wrong:

• B (Error-based): Relies on the database returning error messages that leak schema/data - the attacker absolutely sees output.
• C (Union-based): Appends a UNION SELECT to extract data directly into the response - highly visible output.
• D (Second-order): Involves injected payload being stored and executed later (e.g., in a stored procedure), but it still typically returns results to the attacker when triggered.

Memory tip: Think "blind = no feedback loop." If the attacker can read results directly, it's not blind. Second-order is about timing of execution (now vs. later), not visibility - don't confuse the two on exam day.

No community discussion yet for this question.