SQL injection in Cybersecurity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is SQL injection?

SQL injection is a security vulnerability where an attacker inserts malicious SQL code into a query, allowing unauthorized access or manipulation of a database.

beginner

How does SQL injection typically happen?

It happens when user input is directly included in SQL queries without proper checks or cleaning, letting attackers add harmful commands.

beginner

Name one common way to prevent SQL injection.

Using prepared statements or parameterized queries, which separate code from data, preventing attackers from changing the query structure.

intermediate

What could be a real-life impact of a successful SQL injection attack?

Attackers might steal sensitive data like passwords, delete important information, or take control of the entire database.

intermediate

Why is input validation alone not enough to stop SQL injection?

Because attackers can find ways to bypass simple checks; combining input validation with prepared statements is safer.

What does SQL injection allow an attacker to do?

A Encrypt user passwords

B Improve website speed

C Backup the database automatically

D Run unauthorized database commands

SQL injection lets attackers run harmful commands on the database without permission.

Which practice helps prevent SQL injection?

A Storing passwords in plain text

B Ignoring user input

C Using prepared statements

D Allowing all input without checks

Prepared statements keep code and data separate, stopping attackers from injecting harmful SQL.

SQL injection attacks usually target which part of an application?

A User interface design

B Database queries

C Network cables

D Operating system files

SQL injection targets the database queries that use user input.

What is a sign that a website might be vulnerable to SQL injection?

A Error messages showing database details

B Fast page loading

C Colorful website design

D Strong password requirements

Detailed error messages can reveal database info that attackers use to exploit SQL injection.

Which of these is NOT a good defense against SQL injection?

A Disabling firewalls

B Escaping user input properly

C Using parameterized queries

D Limiting database user permissions

Disabling firewalls weakens security and does not help prevent SQL injection.

Explain what SQL injection is and why it is dangerous.

Think about how attackers use input fields to run harmful database commands.

Describe at least two methods to prevent SQL injection attacks.

Consider how separating code from data and checking inputs helps.

Practice

1. What is SQL injection in cybersecurity?

easy

A. A method to speed up database queries

B. A way to backup database data securely

C. A technique to trick databases into running harmful commands

D. A process to encrypt database connections

Solution

1. Step 1: Understand SQL injection meaning

   SQL injection is a cyberattack where harmful commands are inserted into database queries.

2. Step 2: Identify correct description

   Only the technique to trick databases into running harmful commands describes this attack method accurately.

3. Final Answer:

   A technique to trick databases into running harmful commands -> Option C

4. Quick Check:

   SQL injection = harmful commands trick [OK]

Hint: SQL injection tricks databases with harmful commands [OK]

Common Mistakes:

• Confusing SQL injection with database backup
• Thinking SQL injection speeds up queries
• Mixing SQL injection with encryption

2. Which of the following is a correct way to prevent SQL injection?

easy

A. Using parameterized queries or prepared statements

B. Directly inserting user input into SQL queries without checks

C. Ignoring user input validation

D. Allowing all user inputs without restrictions

Solution

1. Step 1: Review prevention methods

   Safe coding practices include using parameterized queries to separate code from data.

2. Step 2: Identify correct prevention

   Using parameterized queries or prepared statements correctly states using parameterized queries or prepared statements to prevent injection.

3. Final Answer:

   Using parameterized queries or prepared statements -> Option A

4. Quick Check:

   Safe queries = parameterized/prepared [OK]

Hint: Use parameterized queries to stop SQL injection [OK]

Common Mistakes:

• Directly inserting unchecked user input
• Skipping input validation
• Assuming all inputs are safe

3. Consider this SQL query in a login system:
SELECT * FROM users WHERE username = 'admin' AND password = 'password123';
What happens if an attacker inputs ' OR '1'='1 as the password?

medium

A. The query returns no results

B. The query causes a syntax error

C. The query only returns the admin user

D. The query returns all users, bypassing password check

Solution

1. Step 1: Analyze injected input effect

   The input ' OR '1'='1' changes the WHERE clause to always true, bypassing password check.

2. Step 2: Understand query result

   Because '1'='1' is always true, the query returns all users, ignoring password.

3. Final Answer:

   The query returns all users, bypassing password check -> Option D

4. Quick Check:

   Injection ' OR '1'='1' = bypass password [OK]

Hint: Injection ' OR '1'='1' bypasses password check [OK]

Common Mistakes:

• Thinking it causes syntax error
• Assuming it returns no results
• Believing it returns only admin user

4. A developer wrote this SQL query:
query = "SELECT * FROM users WHERE name = '" + user_input + "';"
What is the main problem with this code?

medium

A. It concatenates user input directly into the query, risking SQL injection

B. It prevents SQL injection by validating input

C. It properly escapes user input

D. It uses parameterized queries correctly

Solution

1. Step 1: Examine query construction

   The code builds the SQL query by adding user input directly into the string.

2. Step 2: Identify security risk

   This direct concatenation allows attackers to inject malicious SQL commands.

3. Final Answer:

   It concatenates user input directly into the query, risking SQL injection -> Option A

4. Quick Check:

   Direct concatenation = SQL injection risk [OK]

Hint: Never concatenate user input directly into SQL queries [OK]

Common Mistakes:

• Assuming concatenation is safe
• Thinking input is automatically escaped
• Believing this code validates input

5. You have a web form that accepts a username to search a database. Which approach best protects against SQL injection when building the query?

hard

A. Use string concatenation with manual input cleaning

B. Use parameterized queries with placeholders for user input

C. Allow all input and filter results after query

D. Disable database error messages only

Solution

1. Step 1: Evaluate protection methods

   Parameterized queries separate code from data, preventing injection regardless of input.

2. Step 2: Compare options

   Use parameterized queries with placeholders for user input uses placeholders safely; other options either rely on unsafe cleaning or do not prevent injection.

3. Final Answer:

   Use parameterized queries with placeholders for user input -> Option B

4. Quick Check:

   Best protection = parameterized queries [OK]

Hint: Always use parameterized queries to prevent injection [OK]

Common Mistakes:

• Relying on manual input cleaning
• Filtering results after query is unsafe
• Only hiding error messages does not protect