Why SQL injection via network in Computer Networks? - Purpose & Use Cases

The Big Idea

What if a simple text box on a website could let hackers control the entire database through the network?

The Scenario

Imagine a website that takes user input from a form and sends it directly to a database over the network without checking it carefully.

Attackers can type special commands instead of normal data, and these commands travel through the network to the database.

The Problem

Manually trusting all user input is risky because attackers can sneak harmful commands into the data.

This can lead to unauthorized access, data theft, or damage, and it is hard to spot these attacks just by looking at network traffic.

The Solution

Using secure coding practices and network protections helps stop harmful commands before they reach the database.

Techniques like input validation, prepared statements, and firewalls filter or block dangerous data traveling over the network.

Before vs After

✗ Before

query = "SELECT * FROM users WHERE name = '" + user_input + "'"

✓ After

query = "SELECT * FROM users WHERE name = ?"; execute(query, [user_input])

What It Enables

It allows safe communication over the network, protecting databases from harmful commands hidden in user input.

Real Life Example

A bank website uses network security and safe queries to prevent hackers from stealing customer data by injecting commands through login forms.

Key Takeaways

SQL injection happens when harmful commands travel through the network to a database.

Manual trust of user input is dangerous and can cause serious security breaches.

Using secure coding and network defenses stops these attacks and keeps data safe.

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