File upload security risks in PHP - Time & Space Complexity

Time Complexity: File upload security risks

O(n)

Understanding Time Complexity

When handling file uploads in PHP, it's important to understand how the code's work grows as more files or larger files are processed.

We want to see how the time to check and save files changes with input size.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Process multiple uploaded files
foreach ($_FILES['uploads']['tmp_name'] as $index => $tmpName) {
    $fileName = $_FILES['uploads']['name'][$index];
    $fileType = $_FILES['uploads']['type'][$index];
    // Simple check for allowed types
    if (in_array($fileType, ['image/jpeg', 'image/png'])) {
        move_uploaded_file($tmpName, '/uploads/' . $fileName);
    }
}
    

This code loops through uploaded files, checks their type, and moves allowed files to a folder.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each uploaded file to check and move it.
• How many times: Once for each file uploaded (depends on number of files).

How Execution Grows With Input

As the number of files increases, the code does more checks and moves more files.

Input Size (n)	Approx. Operations
10	About 10 checks and moves
100	About 100 checks and moves
1000	About 1000 checks and moves

Pattern observation: The work grows directly with the number of files; double the files, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to process files grows linearly with how many files are uploaded.

Common Mistake

[X] Wrong: "Checking file types or moving files happens instantly no matter how many files there are."

[OK] Correct: Each file requires a check and a move operation, so more files mean more work and more time.

Interview Connect

Understanding how file upload handling scales helps you write safer and more efficient code, a skill valuable in many real projects.

Self-Check

"What if we added a nested loop to scan inside each file's contents? How would the time complexity change?"

Practice

1. Which of the following is the most important reason to validate file types during a PHP file upload?

easy

A. To make the upload process faster

B. To allow uploading any file without restrictions

C. To reduce server storage space

D. To prevent users from uploading harmful scripts disguised as files

Solution

1. Step 1: Understand file upload risks

   Malicious users can upload harmful scripts if file types are not checked.

2. Step 2: Importance of validation

   Validating file types helps block dangerous files and protects the server.

3. Final Answer:

   To prevent users from uploading harmful scripts disguised as files -> Option D

4. Quick Check:

   File type validation = prevent harmful uploads [OK]

Hint: Always check file types to block dangerous uploads [OK]

Common Mistakes:

• Ignoring file type validation
• Assuming all files are safe
• Only checking file extensions without content

2. Which PHP function is commonly used to check the MIME type of an uploaded file for security?

easy

A. mime_content_type()

B. is_uploaded_file()

C. file_get_contents()

D. move_uploaded_file()

Solution

1. Step 1: Identify function purpose

   mime_content_type() returns the MIME type of a file, useful for validation.

2. Step 2: Compare with other functions

   move_uploaded_file() moves files, file_get_contents() reads content, is_uploaded_file() checks upload status.

3. Final Answer:

   mime_content_type() -> Option A

4. Quick Check:

   Check MIME type = mime_content_type() [OK]

Hint: Use mime_content_type() to verify file type safely [OK]

Common Mistakes:

• Using move_uploaded_file() to check file type
• Confusing file_get_contents() with type checking
• Not verifying MIME type at all

3. What will be the output of this PHP code snippet if a user uploads a file named image.jpg with size 5MB, but the allowed max size is 2MB?

$maxSize = 2 * 1024 * 1024; // 2MB
if ($_FILES['file']['size'] > $maxSize) {
    echo 'File too large';
} else {
    echo 'Upload successful';
}

medium

A. File too large

B. Upload successful

C. No output

D. Syntax error

Solution

1. Step 1: Understand size check logic

   The code compares uploaded file size to maxSize (2MB).

2. Step 2: Compare actual file size

   Uploaded file is 5MB, which is greater than 2MB, so condition is true.

3. Final Answer:

   File too large -> Option A

4. Quick Check:

   5MB > 2MB triggers 'File too large' [OK]

Hint: Compare file size with max allowed size [OK]

Common Mistakes:

• Confusing bytes and megabytes
• Not multiplying correctly for max size
• Ignoring file size check

4. Identify the security issue in this PHP file upload code snippet:

if (move_uploaded_file($_FILES['file']['tmp_name'], 'uploads/' . $_FILES['file']['name'])) {
    echo 'Upload successful';
} else {
    echo 'Upload failed';
}

medium

A. Using original filename without sanitization

B. All of the above

C. Missing check if file is uploaded via HTTP POST

D. No file size check before upload

Solution

1. Step 1: Check file size validation

   Code does not check file size before moving the file.

2. Step 2: Check filename handling

   Using original filename directly risks overwriting and security issues.

3. Step 3: Check upload method validation

   Missing is_uploaded_file() check to confirm HTTP POST upload.

4. Final Answer:

   All of the above -> Option B

5. Quick Check:

   Missing size, sanitization, and upload checks [OK]

Hint: Check size, sanitize name, verify upload method [OK]

Common Mistakes:

• Ignoring filename sanitization
• Not verifying upload method
• Skipping file size validation

5. You want to securely handle file uploads in PHP by allowing only PNG images under 1MB, renaming files to a unique name, and preventing script execution. Which combination of steps is best?

hard

A. Check file size, move file with original name, allow all image types

B. Only check file extension, rename file, save in uploads folder

C. Check MIME type with mime_content_type(), limit size, rename with uniqid(), save outside web root

D. Skip validation, rename file, save in web root

Solution

1. Step 1: Validate file type and size

   Use mime_content_type() to confirm PNG and check size under 1MB.

2. Step 2: Rename file and secure storage

   Rename with uniqid() to avoid conflicts and save outside web root to prevent script execution.

3. Final Answer:

   Check MIME type with mime_content_type(), limit size, rename with uniqid(), save outside web root -> Option C

4. Quick Check:

   Validate type & size + rename + secure storage [OK]

Hint: Validate type/size, rename uniquely, store securely [OK]

Common Mistakes:

• Relying only on file extension
• Saving files in web root without restrictions
• Not renaming files uniquely