Cross-site request forgery (CSRF) in Cybersecurity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the type of attack described.

Cybersecurity

An attack where unauthorized commands are transmitted from a user that the web application trusts is called [1].

Drag options to blanks, or click blank then click option'

ACross-site request forgery

BSQL Injection

CPhishing

DDenial of Service

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing CSRF with SQL Injection.

Thinking it is a phishing attack.

Cross-site request forgery (CSRF) tricks a user into submitting unwanted actions on a web application where they are authenticated.

2fill in blank

medium

Complete the code to describe a common defense against CSRF.

Cybersecurity

A common defense against CSRF attacks is to use a [1] token that is unique to each user session.

Drag options to blanks, or click blank then click option'

Acaptcha

Bpassword

CCSRF

Dsession

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'password' instead of the correct token.

Confusing CSRF token with captcha.

A CSRF token is a secret, unique value sent with requests to verify the request is legitimate.

3fill in blank

hard

Fix the error in the description of CSRF protection.

Cybersecurity

To protect against CSRF, the server should check if the request includes a valid [1] token matching the user's session.

Drag options to blanks, or click blank then click option'

AIP address

BCSRF

Cpassword

Dcookie

Attempts:

3 left

💡 Hint

Common Mistakes

Checking only cookies or IP addresses.

Using password instead of CSRF token.

The server verifies the CSRF token to ensure the request is from the legitimate user.

4fill in blank

hard

Fill both blanks to complete the explanation of how CSRF tokens work.

Cybersecurity

The server generates a [1] token and includes it in the [2] form to verify legitimate requests.

Drag options to blanks, or click blank then click option'

ACSRF

Bhidden

Cpassword

Dvisible

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'password' instead of CSRF for the token.

Placing the token in a visible form field.

The CSRF token is a secret value included as a hidden field in forms to validate requests.

5fill in blank

hard

Fill all three blanks to complete the code snippet that checks CSRF token validity.

Cybersecurity

if request.method == 'POST' and request.form.get('[1]') == session.get('[2]'):
    process_request()
else:
    raise [3]('Invalid CSRF token')

Drag options to blanks, or click blank then click option'

Acsrf_token

CSecurityError

DValueError

Attempts:

3 left

💡 Hint

Common Mistakes

Using different token names in form and session.

Raising a generic error instead of a security-specific one.

The code compares the CSRF token from the form with the one stored in the session. If they don't match, it raises a security error.

Practice

1. What is the main goal of a Cross-site request forgery (CSRF) attack?

easy

A. To encrypt user data for ransom

B. To steal a user's password by phishing

C. To overload a website with traffic causing it to crash

D. To trick a logged-in user into performing unwanted actions on a website

Solution

1. Step 1: Understand CSRF attack purpose

   CSRF attacks aim to make a user unknowingly perform actions they did not intend on a trusted website.

2. Step 2: Compare with other attack types

   Phishing steals passwords, DoS overloads servers, and ransomware encrypts data, which are different from CSRF.

3. Final Answer:

   To trick a logged-in user into performing unwanted actions on a website -> Option D

4. Quick Check:

   CSRF = trick user actions [OK]

Hint: CSRF tricks users into unwanted website actions [OK]

Common Mistakes:

• Confusing CSRF with phishing attacks
• Thinking CSRF steals passwords directly
• Mixing CSRF with denial-of-service attacks

2. Which of the following is a common method to protect a website against CSRF attacks?

easy

A. Blocking all cookies from the browser

B. Encrypting all user passwords with SHA-1

C. Using secret tokens that must be submitted with requests

D. Disabling JavaScript on the website

Solution

1. Step 1: Identify CSRF protection techniques

   Websites use secret tokens (CSRF tokens) that must be included in requests to verify they come from the user intentionally.

2. Step 2: Eliminate unrelated options

   Encrypting passwords, blocking cookies, or disabling JavaScript do not specifically prevent CSRF attacks.

3. Final Answer:

   Using secret tokens that must be submitted with requests -> Option C

4. Quick Check:

   CSRF protection = secret tokens [OK]

Hint: CSRF defense uses secret tokens in requests [OK]

Common Mistakes:

• Thinking password encryption stops CSRF
• Believing blocking cookies prevents CSRF
• Assuming disabling JavaScript is a CSRF fix

3. Consider this scenario: A user is logged into their bank website. An attacker sends a hidden form on another site that submits a money transfer request to the bank without the user's knowledge. Which security measure would stop this CSRF attack?

medium

A. The bank requires a unique CSRF token with each form submission

B. The bank uses HTTPS for all pages

C. The bank requires a strong password

D. The bank limits login attempts

Solution

1. Step 1: Analyze the attack method

   The attacker tricks the user into submitting a form without their consent, typical of CSRF.

2. Step 2: Identify effective defense

   Requiring a unique CSRF token ensures the form submission is legitimate and from the user, blocking forged requests.

3. Final Answer:

   The bank requires a unique CSRF token with each form submission -> Option A

4. Quick Check:

   CSRF blocked by unique tokens [OK]

Hint: Unique CSRF tokens stop forged form submissions [OK]

Common Mistakes:

• Thinking HTTPS alone stops CSRF
• Believing strong passwords prevent CSRF
• Confusing login limits with CSRF defense

4. A developer wrote this code snippet to protect against CSRF:

<form method="POST" action="/transfer">
  <input type="hidden" name="csrf_token" value="12345" />
  <input type="submit" value="Send" />
</form>

Why might this code still be vulnerable to CSRF attacks?

medium

A. The form uses POST method instead of GET

B. The CSRF token is static and not unique per user session

C. The form does not include a CAPTCHA

D. The form action URL is relative

Solution

1. Step 1: Examine the CSRF token usage

   The token value "12345" is hardcoded and does not change per user or session, making it predictable.

2. Step 2: Understand CSRF token requirements

   Effective CSRF tokens must be unique and unpredictable per user session to prevent attackers from guessing them.

3. Final Answer:

   The CSRF token is static and not unique per user session -> Option B

4. Quick Check:

   Static tokens fail CSRF protection [OK]

Hint: CSRF tokens must be unique per session, not static [OK]

Common Mistakes:

• Thinking POST method alone prevents CSRF
• Assuming CAPTCHA is required for CSRF defense
• Believing relative URLs cause CSRF vulnerabilities

5. A website uses cookies for user sessions but does not implement CSRF tokens. An attacker crafts a malicious link that triggers a fund transfer when clicked by a logged-in user. How can the website improve security to prevent this CSRF attack without removing cookies?

hard

A. Implement a unique CSRF token that must be submitted with sensitive requests

B. Switch all requests to use GET method instead of POST

C. Require users to re-enter their password on every page load

D. Disable cookies and use URL parameters for sessions

Solution

1. Step 1: Identify the vulnerability

   Cookies alone do not prevent CSRF because browsers send them automatically with requests, allowing forged actions.

2. Step 2: Choose effective mitigation

   Adding unique CSRF tokens ensures that only legitimate requests from the user are accepted, blocking forged requests.

3. Final Answer:

   Implement a unique CSRF token that must be submitted with sensitive requests -> Option A

4. Quick Check:

   Unique tokens prevent CSRF despite cookies [OK]

Hint: Add unique CSRF tokens to protect cookie-based sessions [OK]

Common Mistakes:

• Thinking GET requests are safer than POST
• Believing password re-entry on every page is practical
• Assuming disabling cookies is the only fix