CSRF protection concept in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does CSRF stand for and what is it?

CSRF stands for Cross-Site Request Forgery. It is a type of attack where a bad website tricks a user's browser into making unwanted actions on a trusted site where the user is logged in.

beginner

How does Flask help protect against CSRF attacks?

Flask uses a CSRF token, a secret value sent with forms. The server checks this token on form submission to make sure the request is from the real user, not a fake site.

beginner

What is a CSRF token and why is it important?

A CSRF token is a unique, secret value generated by the server and included in forms. It helps confirm that the form submission is genuine and not forged by another site.

intermediate

Which Flask extension is commonly used to add CSRF protection?

Flask-WTF is a popular extension that adds CSRF protection automatically by generating and validating CSRF tokens in forms.

beginner

Why is it important to include CSRF protection in web forms?

Without CSRF protection, attackers can trick users into submitting forms unknowingly, causing unwanted actions like changing passwords or making purchases.

What does a CSRF token do in a Flask app?

A Verifies that form submissions come from the real user

B Encrypts user passwords

C Stores user session data

D Prevents SQL injection attacks

A CSRF token confirms that the form submission is genuine and not forged by another site.

Which Flask extension helps with CSRF protection?

A Flask-Login

B Flask-SQLAlchemy

C Flask-WTF

D Flask-Migrate

Flask-WTF automatically adds CSRF tokens to forms and validates them.

CSRF attacks happen because:

A Forms use GET instead of POST

B Users forget their passwords

C Servers do not encrypt data

D Browsers trust requests from logged-in users without extra checks

Browsers send cookies automatically, so attackers can trick browsers into sending unwanted requests if no CSRF protection exists.

What must a server check to prevent CSRF?

A User's IP address

B Presence and validity of CSRF token

C User's browser type

D Form field lengths

The server checks the CSRF token to confirm the request is legitimate.

Which HTTP method is most commonly protected by CSRF tokens?

A POST

B GET

C HEAD

D OPTIONS

POST requests change data and are protected by CSRF tokens to prevent forged submissions.

Explain in simple terms what CSRF protection is and why it matters in Flask web apps.

Think about how a bad website might trick a logged-in user to do something unwanted.

Describe how to add CSRF protection to a Flask form using Flask-WTF.

Focus on the steps to set up and use the extension.

Practice

1. What is the main purpose of CSRF protection in a Flask web application?

easy

A. To speed up the loading time of web pages

B. To encrypt user passwords in the database

C. To prevent attackers from making users perform unwanted actions without their consent

D. To improve the visual design of forms

Solution

1. Step 1: Understand what CSRF stands for

   CSRF means Cross-Site Request Forgery, which tricks users into submitting unwanted requests.

2. Step 2: Identify the purpose of CSRF protection

   CSRF protection stops attackers from forcing users to perform actions they did not intend.

3. Final Answer:

   To prevent attackers from making users perform unwanted actions without their consent -> Option C

4. Quick Check:

   CSRF protection = prevent unwanted user actions [OK]

Hint: CSRF stops fake actions from attackers using your login [OK]

Common Mistakes:

• Confusing CSRF with password encryption
• Thinking CSRF improves page speed
• Believing CSRF changes form appearance

2. Which of the following is the correct way to enable CSRF protection in a Flask app using Flask-WTF?

easy

A. from flask_wtf import CSRFProtect
app = Flask(__name__)
csrf = CSRFProtect(app)
csrf.init_app(app)

B. from flask_wtf import CSRFProtect
csrf = CSRFProtect()
app = Flask(__name__)

C. app = Flask(__name__)
app.csrf = True

D. from flask_wtf import CSRFProtect
csrf = CSRFProtect(app)

Solution

1. Step 1: Recall Flask-WTF CSRF setup

   You import CSRFProtect and pass the Flask app instance to it to enable protection.

2. Step 2: Check the options for correct syntax

   from flask_wtf import CSRFProtect csrf = CSRFProtect(app) correctly imports CSRFProtect and initializes it with the app in one step.

3. Final Answer:

   from flask_wtf import CSRFProtect csrf = CSRFProtect(app) -> Option D

4. Quick Check:

   CSRFProtect(app) initializes protection [OK]

Hint: Initialize CSRFProtect with app instance directly [OK]

Common Mistakes:

• Calling CSRFProtect without passing app
• Setting app.csrf = True (not valid)
• Calling init_app after passing app (redundant)

3. Given this Flask route with CSRF protection enabled, what happens if the form is submitted without a CSRF token?

@app.route('/submit', methods=['POST'])
def submit():
    return 'Success'

medium

A. The server raises a CSRF error and rejects the request

B. The server ignores the CSRF token and processes normally

C. The request is accepted and returns 'Success'

D. The server redirects to the home page without error

Solution

1. Step 1: Understand CSRF token role in POST requests

   CSRF tokens verify that the form submission is from a trusted source.

2. Step 2: Check behavior when token is missing

   Without a valid CSRF token, Flask-WTF raises an error and rejects the request.

3. Final Answer:

   The server raises a CSRF error and rejects the request -> Option A

4. Quick Check:

   Missing CSRF token = error rejection [OK]

Hint: POST without token triggers CSRF error [OK]

Common Mistakes:

• Assuming request is accepted without token
• Thinking server silently ignores missing token
• Believing server redirects instead of error

4. You added CSRF protection to your Flask app but get a 'CSRF token missing' error on form submission. Which fix will solve this issue?

medium

A. Add {{ form.csrf_token }} inside the HTML form

B. Remove the CSRFProtect initialization from the app

C. Change the form method to GET instead of POST

D. Disable CSRF protection in Flask-WTF config

Solution

1. Step 1: Identify cause of missing CSRF token

   The form must include the CSRF token field to send it with the request.

2. Step 2: Choose the fix that adds the token to the form

   Adding {{ form.csrf_token }} in the form template includes the token correctly.

3. Final Answer:

   Add {{ form.csrf_token }} inside the HTML form -> Option A

4. Quick Check:

   Include CSRF token in form to fix error [OK]

Hint: Always include {{ form.csrf_token }} in your forms [OK]

Common Mistakes:

• Removing CSRF protection instead of fixing token
• Changing POST to GET (not secure)
• Disabling CSRF protection globally

5. You want to protect a Flask route that updates user data via POST. Which combination correctly applies CSRF protection and form token usage?

hard

A. Use CSRFProtect(app) but omit the token in the form for simplicity

B. Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form

C. Skip CSRFProtect and rely on session cookies only

D. Add {{ form.csrf_token }} in form but do not enable CSRFProtect in app

Solution

1. Step 1: Understand CSRF protection requirements

   Both enabling CSRFProtect in the app and including the token in the form are needed to protect POST routes.

2. Step 2: Evaluate each option for completeness

   Only Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form correctly enables protection and includes the token in the form.

3. Final Answer:

   Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form -> Option B

4. Quick Check:

   Protect POST routes with CSRFProtect and token [OK]

Hint: Both app and form need CSRF setup for protection [OK]

Common Mistakes:

• Enabling protection but missing token in form
• Including token but not enabling protection
• Relying only on session cookies