SQL injection via network in Computer Networks - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is SQL injection?

SQL injection is a type of security attack where an attacker inserts malicious SQL code into a query to manipulate a database.

beginner

How can SQL injection happen over a network?

SQL injection over a network happens when an attacker sends malicious input through network requests to a server that runs SQL queries without proper checks.

intermediate

Name a common way attackers exploit SQL injection via network.

Attackers often exploit web forms or URL parameters that send data to a server, injecting SQL commands through these inputs.

beginner

What is a simple method to prevent SQL injection attacks?

Using prepared statements or parameterized queries ensures user input is treated as data, not code, preventing SQL injection.

intermediate

Why is monitoring network traffic important for detecting SQL injection?

Monitoring network traffic helps spot unusual or suspicious requests that may contain SQL injection attempts, allowing early defense.

What does SQL injection allow an attacker to do?

A Encrypt database contents

B Increase network speed

C Backup data automatically

D Manipulate or steal data from a database

SQL injection lets attackers insert harmful SQL code to change or access data they shouldn't.

Which input is commonly targeted for SQL injection over a network?

A Printer configurations

B User input fields in web forms

C Screen resolution settings

D Network cable quality

Attackers use user input fields like forms or URL parameters to inject malicious SQL commands.

What is a key defense against SQL injection?

A Using parameterized queries

B Disabling the internet

C Increasing server RAM

D Changing screen colors

Parameterized queries separate code from data, stopping attackers from injecting SQL code.

How can SQL injection attacks be detected on a network?

A By monitoring network traffic for suspicious requests

B By checking printer status

C By updating screen drivers

D By increasing bandwidth

Monitoring network traffic helps find unusual requests that may be SQL injection attempts.

SQL injection attacks usually target which part of a system?

A Keyboard layout

B Monitor brightness

C Database queries

D Mouse sensitivity

SQL injection attacks focus on manipulating database queries to access or change data.

Explain how SQL injection can occur through network communication.

Think about how data sent over the network can be harmful if not checked.

Describe methods to prevent SQL injection attacks in networked applications.

Focus on how to safely handle user input and watch for attacks.

Practice

1. What is SQL injection via network in simple terms?

easy

A. A way to backup database data remotely

B. A method to speed up database queries over the network

C. An attack where harmful commands are sent to a database through a network connection

D. A network protocol for secure database communication

Solution

1. Step 1: Understand the meaning of SQL injection

   SQL injection means sending harmful commands to a database to manipulate or steal data.

2. Step 2: Connect SQL injection with network

   When these harmful commands are sent through a network connection, it is called SQL injection via network.

3. Final Answer:

   An attack where harmful commands are sent to a database through a network connection -> Option C

4. Quick Check:

   SQL injection via network = harmful commands sent over network [OK]

Hint: Think: harmful commands sent through network to database [OK]

Common Mistakes:

• Confusing SQL injection with normal database queries
• Thinking it is a backup or speed method
• Mixing it up with network security protocols

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

easy

A. Use input validation and parameterized queries

B. Send raw SQL commands directly over the network

C. Disable network connections to the database

D. Allow all user inputs without checks

Solution

1. Step 1: Identify safe practices against SQL injection

   Input validation checks user data, and parameterized queries separate data from commands, preventing injection.

2. Step 2: Evaluate other options

   Sending raw commands or allowing unchecked inputs increases risk; disabling network is impractical.

3. Final Answer:

   Use input validation and parameterized queries -> Option A

4. Quick Check:

   Safe coding = input validation + parameterized queries [OK]

Hint: Prevent injection by validating inputs and using safe queries [OK]

Common Mistakes:

• Thinking disabling network is practical
• Believing raw SQL commands are safe
• Ignoring input validation importance

3. Consider this SQL query sent over a network: SELECT * FROM users WHERE username = '' OR '1'='1';. What is the likely result?

medium

A. Causes the database to crash

B. Returns no users because of syntax error

C. Returns only users with empty username

D. Returns all users because the condition is always true

Solution

1. Step 1: Analyze the SQL condition

   The condition username = '' OR '1'='1' means either username is empty or '1' equals '1'. Since '1'='1' is always true, the whole condition is true for all rows.

2. Step 2: Understand query effect

   Because the WHERE clause is always true, the query returns all users from the table.

3. Final Answer:

   Returns all users because the condition is always true -> Option D

4. Quick Check:

   Always true condition returns all rows [OK]

Hint: Look for always true conditions like '1'='1' [OK]

Common Mistakes:

• Assuming syntax error due to quotes
• Thinking it returns no rows
• Believing it crashes the database

4. A developer wrote this query to get user info: "SELECT * FROM users WHERE id = " + user_input; sent over network. What is the main problem?

medium

A. It concatenates user input directly, risking SQL injection

B. It uses prepared statements safely

C. It uses parameterized queries correctly

D. It encrypts user input before sending

Solution

1. Step 1: Examine how user input is used

   The query concatenates user input directly into the SQL string, which can allow attackers to insert harmful commands.

2. Step 2: Identify risk of SQL injection

   Direct concatenation without validation or parameterization is a common cause of SQL injection vulnerabilities.

3. Final Answer:

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

4. Quick Check:

   Direct input concatenation = injection risk [OK]

Hint: Avoid direct string concatenation with user input [OK]

Common Mistakes:

• Thinking concatenation is safe
• Confusing with parameterized queries
• Assuming encryption is done automatically

5. You receive a network log showing this suspicious query: SELECT * FROM accounts WHERE user = 'admin'--' AND password = 'anything'; What does the -- do in this SQL injection attempt?

hard

A. Encrypts the password part of the query

B. Comments out the rest of the query, bypassing password check

C. Ends the SQL statement safely

D. Causes a syntax error and stops execution

Solution

1. Step 1: Understand the role of -- in SQL

   The -- sequence starts a comment in SQL, ignoring everything after it on the same line.

2. Step 2: Analyze the effect on the query

   By commenting out the password check, the attacker bypasses authentication, gaining access as 'admin'.

3. Final Answer:

   Comments out the rest of the query, bypassing password check -> Option B

4. Quick Check:

   -- = comment to skip code [OK]

Hint: Remember -- starts a comment in SQL [OK]

Common Mistakes:

• Thinking -- encrypts or ends query safely
• Assuming it causes syntax error
• Not realizing it bypasses checks