Skip to content

Interview question · Application & API Security

Why does the database account's privilege decide how bad an SQL injection becomes, and how do you limit the blast radius?

The same injection bug can leak one table or hand over the server. The difference is decided by grants made long before the bug was written.

mediumNewPreparation tags: Microsoft, Amazon, GoogleUpdated Nov 2026

The same injection bug can leak one table or hand over the server. The difference is decided by grants made long before the bug was written.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 6 follow-ups like an interviewer would

A penetration tester finds a blind SQL injection in a search endpoint of a legacy app that connects to the database as the administrator account.

  1. Why does the database account matter for severity?
  2. What does a read-only, view-limited account limit it to?
  3. What does an administrator account allow?
  4. What do you do immediately?
  5. How would you prevent this elsewhere?
  6. How would you handle the finding?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.