Security best practices in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Laravel's CSRF protection?

Laravel includes CSRF protection by default. What does this protect your application from?

A Prevent attackers from submitting forms on behalf of authenticated users without their consent.

B Encrypt user passwords before saving them to the database.

C Limit the number of login attempts to prevent brute force attacks.

D Stop SQL injection attacks by escaping database queries.

💡 Hint

Think about what happens if a malicious site tries to submit a form on your site without permission.

CSRF (Cross-Site Request Forgery) protection prevents unauthorized commands from being transmitted from a user that the web application trusts. Laravel uses tokens to verify that form submissions come from the actual user.

❓ component_behavior

intermediate

What happens if you forget to validate user input in a Laravel controller?

Consider a Laravel controller method that processes user input but does not validate it. What is the most likely risk?

Laravel

public function store(Request $request) {
    $data = $request->all();
    User::create($data);
    return redirect('/users');
}

A The application will run slower but remain secure.

B Laravel will automatically reject the request and show an error page.

C The user input will be sanitized automatically by Laravel.

D The application may save invalid or malicious data, leading to security issues like SQL injection or broken data.

💡 Hint

Think about what happens when you trust user input without checking it.

Without validation, malicious or incorrect data can be saved, potentially causing security vulnerabilities or corrupting the database. Laravel does not sanitize or validate input automatically.

📝 Syntax

advanced

Which code snippet correctly hashes a password before saving a new user in Laravel?

Choose the code that securely hashes the password before saving it to the database.

A User::create(['name' => $name, 'email' => $email, 'password' => hash('sha256', $password)]);

B User::create(['name' => $name, 'email' => $email, 'password' => $password]);

C User::create(['name' => $name, 'email' => $email, 'password' => bcrypt($password)]);

D User::create(['name' => $name, 'email' => $email, 'password' => md5($password)]);

💡 Hint

Laravel provides a helper function specifically for hashing passwords securely.

Laravel's bcrypt() helper hashes passwords using the bcrypt algorithm, which is secure and recommended. Using raw hashes like sha256 or md5 is insecure for passwords.

🔧 Debug

advanced

Why does this Laravel middleware fail to block unauthenticated users?

Review the middleware code below. Why does it not redirect unauthenticated users to the login page?

Laravel

public function handle($request, Closure $next) {
    if (!Auth::check()) {
        return redirect('/login');
    }
    return $next($request);
}

A The middleware does not return the result of $next($request), so the request continues without redirecting.

B Auth::check() always returns true, so the condition never triggers.

C The redirect URL '/login' is incorrect and causes a 404 error.

D Middleware must be registered in the kernel to work, so this code never runs.

💡 Hint

Look carefully at the last line inside the handle method.

The middleware must return the result of $next($request) to continue the request lifecycle. Without returning it, the middleware does not properly pass control, causing unexpected behavior.

❓ lifecycle

expert

At which point in Laravel's request lifecycle is the encryption of cookies handled?

Identify when Laravel encrypts cookies during the request lifecycle.

A After the controller returns a response, just before sending it to the browser.

B During the EncryptCookies middleware, which runs before the request reaches the controller.

C When the cookies are accessed inside the controller method.

D Cookies are never encrypted automatically by Laravel.

💡 Hint

Think about middleware order and what EncryptCookies does.

Laravel encrypts cookies in the EncryptCookies middleware, which runs early in the request lifecycle before the controller handles the request. This ensures cookies are encrypted and decrypted automatically.