How string concatenation creates vulnerabilities in SQL - Why You Should Know This

The Big Idea

Could a simple text input be the key to unlocking your entire database?

The Scenario

Imagine you want to build a search feature on a website. You write code that takes what users type and adds it directly into a database command by joining text pieces together.

For example, you write: SELECT * FROM users WHERE name = '" + userInput + "';

This looks simple and quick to do.

The Problem

But this way is risky. If someone types strange or harmful text, it can trick your database into doing things you never wanted.

This can let attackers see secret data, change or delete information, or even break your whole system.

Manually joining strings like this is slow to fix and easy to get wrong.

The Solution

Instead, using safe methods like prepared statements or parameterized queries keeps user input separate from commands.

This stops attackers from changing the meaning of your commands, making your app much safer.

Before vs After

✗ Before

query = "SELECT * FROM users WHERE name = '" + userInput + "';"

✓ After

query = "SELECT * FROM users WHERE name = ?"; // then bind userInput safely

What It Enables

It lets you safely accept user input without risking your database security or data integrity.

Real Life Example

A login form that checks usernames and passwords without letting attackers bypass login or steal data.

Key Takeaways

Manually joining strings for database commands is risky and error-prone.

Attackers can exploit this to harm your data or system.

Using safe query methods protects your app and users.

Practice

1. What is the main security risk when using string concatenation to build SQL queries?

easy

A. It can allow attackers to inject malicious SQL code.

B. It makes queries run faster than parameterized queries.

C. It automatically encrypts user input.

D. It prevents any syntax errors in the query.

Solution

1. Step 1: Understand string concatenation in SQL queries

   Concatenating user input directly into SQL commands can mix code and data.

2. Step 2: Recognize the risk of SQL injection

   This mixing allows attackers to add harmful SQL commands, called SQL injection.

3. Final Answer:

   It can allow attackers to inject malicious SQL code. -> Option A

4. Quick Check:

   SQL injection risk = A [OK]

Hint: Concatenating user input risks injection attacks [OK]

Common Mistakes:

• Thinking concatenation speeds up queries
• Believing concatenation encrypts input
• Assuming concatenation prevents errors

2. Which of the following SQL query constructions using string concatenation is syntactically correct?

easy

A. SELECT * FROM users WHERE name = '\'' + userName + '\'';

B. SELECT * FROM users WHERE name = '\'' + userName + '\'

C. SELECT * FROM users WHERE name = ' + userName + "';

D. SELECT * FROM users WHERE name = '\'' + userName + "';

Solution

1. Step 1: Check string delimiters and concatenation syntax

   In SQL, string literals are enclosed in single quotes. Concatenation in code requires proper quotes and plus signs.

2. Step 2: Identify correct syntax for concatenation in code

   SELECT * FROM users WHERE name = '\'' + userName + '\''; correctly escapes single quotes for SQL string literals and concatenates userName with plus signs.

3. Final Answer:

   "SELECT * FROM users WHERE name = '\'' + userName + '\'';" -> Option A

4. Quick Check:

   Proper quotes and concatenation = A [OK]

Hint: Look for matching quotes and plus signs [OK]

Common Mistakes:

• Missing semicolon at end
• Mismatched or missing quotes
• Using wrong concatenation operators

3. Given the query built by concatenation: "SELECT * FROM users WHERE username = '" + input + "';" and input = admin' OR '1'='1, what will be the effect when executed?

medium

A. Returns only the user with username 'admin'.

B. Returns all users because the WHERE clause is always true.

C. Causes a syntax error and query fails.

D. Returns no rows because input is invalid.

Solution

1. Step 1: Substitute input into the query string

   The query becomes: SELECT * FROM users WHERE username = 'admin' OR '1'='1';

2. Step 2: Analyze the WHERE clause logic

   The condition '1'='1' is always true, so the WHERE clause matches all rows.

3. Final Answer:

   Returns all users because the WHERE clause is always true. -> Option B

4. Quick Check:

   Injected OR '1'='1' returns all rows = D [OK]

Hint: Injected OR '1'='1' makes WHERE always true [OK]

Common Mistakes:

• Thinking it returns only 'admin'
• Assuming syntax error occurs
• Believing no rows are returned

4. Identify the error in this SQL query construction using string concatenation: query = "SELECT * FROM users WHERE id = " + userId; where userId is a string input.

medium

A. Using plus sign for concatenation is invalid in SQL.

B. No error; query is correct.

C. Query is safe from SQL injection.

D. Missing quotes around userId value causing syntax error.

Solution

1. Step 1: Check how userId is inserted in query

   The query concatenates userId without quotes, so if userId is a string, SQL syntax breaks.

2. Step 2: Understand SQL string literal requirements

   String values must be enclosed in single quotes in SQL to be valid.

3. Final Answer:

   Missing quotes around userId value causing syntax error. -> Option D

4. Quick Check:

   String values need quotes = B [OK]

Hint: String inputs need quotes in SQL queries [OK]

Common Mistakes:

• Thinking plus sign is invalid in code
• Assuming query is safe from injection
• Ignoring missing quotes causes errors

5. You want to prevent SQL injection when building queries with user input. Which approach best avoids vulnerabilities caused by string concatenation?

hard

A. Remove all spaces from user input before concatenation.

B. Escape all single quotes in user input manually before concatenation.

C. Use parameterized queries or prepared statements instead of concatenation.

D. Convert user input to uppercase before concatenation.

Solution

1. Step 1: Understand the problem with string concatenation

   Concatenation mixes code and data, allowing injection if input is malicious.

2. Step 2: Identify secure alternatives

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

3. Final Answer:

   Use parameterized queries or prepared statements instead of concatenation. -> Option C

4. Quick Check:

   Parameterized queries prevent injection = C [OK]

Hint: Always prefer parameterized queries over concatenation [OK]

Common Mistakes:

• Relying on manual escaping which is error-prone
• Thinking removing spaces prevents injection
• Assuming uppercase conversion secures input