SQL injection via network in Computer Networks - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding SQL Injection Basics

What is the primary goal of an SQL injection attack when performed over a network?

A To insert malicious SQL code into a query to manipulate the database

B To physically damage the network hardware

C To encrypt network traffic for secure communication

D To block all incoming network connections

💡 Hint

Think about what SQL injection tries to do with database queries.

SQL injection aims to insert harmful SQL commands into input fields or network requests to trick the database into executing unintended commands.

📋 Factual

intermediate

Common Network Vectors for SQL Injection

Which network protocol is most commonly exploited to deliver SQL injection attacks?

A SMTP

B FTP

C HTTP

D DNS

💡 Hint

Consider which protocol is used for web applications where SQL injection is frequent.

HTTP is the protocol used by web applications, which often accept user input that can be exploited for SQL injection.

🚀 Application

advanced

Detecting SQL Injection via Network Traffic

You are monitoring network traffic and see a URL parameter with this value: id=1 OR 1=1. What does this suggest?

A A normal URL parameter with no risk

B An encrypted value for secure transmission

C A network error causing corrupted data

D A possible SQL injection attempt trying to bypass authentication

💡 Hint

Think about what OR 1=1 does in SQL queries.

The condition OR 1=1 always evaluates to true, which attackers use to trick the database into returning all records or bypassing checks.

🔍 Analysis

advanced

Impact of SQL Injection on Networked Systems

Which of the following is NOT a typical consequence of a successful SQL injection attack over a network?

A Physical destruction of network cables

B Data corruption or deletion

C Unauthorized data access

D Bypassing authentication controls

💡 Hint

Consider what SQL injection can and cannot do to physical network components.

SQL injection affects data and database logic but cannot physically damage hardware like cables.

❓ Reasoning

expert

Preventing SQL Injection in Networked Applications

Which method is the most effective to prevent SQL injection attacks transmitted over a network?

A Increasing network bandwidth

B Using parameterized queries or prepared statements

C Blocking all incoming network connections

D Encrypting network traffic with SSL/TLS

💡 Hint

Think about how to safely handle user input in database queries.

Parameterized queries separate code from data, preventing attackers from injecting malicious SQL commands.

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