Why security is critical in Flask - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Flask class.

Flask

from flask import [1]
app = [1](__name__)

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

Arender_template

BRequest

CFlask

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of Flask

Using render_template in place of Flask

The Flask class is imported to create the app instance.

2fill in blank

medium

Complete the code to define a route for the home page.

Flask

@app.route('[1]')
def home():
    return 'Welcome to the secure app!'

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

A/

B/home

C/index.html

D/main

Attempts:

3 left

💡 Hint

Common Mistakes

Using '/home' instead of '/'

Using file names like '/index.html'

The root URL '/' is used for the home page route.

3fill in blank

hard

Fix the error in the code to run the Flask app securely.

Flask

if __name__ == '__main__':
    app.run(debug=[1])

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

ATrue

BNone

C0

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving debug=True in production

Using None or 0 instead of False

Debug mode should be off (False) in production for security.

4fill in blank

hard

Fill both blanks to protect against Cross-Site Request Forgery (CSRF).

Flask

from flask_wtf import [1]
app.config['SECRET_KEY'] = '[2]'

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

ACSRFProtect

BFlaskForm

Chard-to-guess-secret-key

DSESSION_COOKIE_SECURE

Attempts:

3 left

💡 Hint

Common Mistakes

Using FlaskForm instead of CSRFProtect for protection

Misconfiguring SECRET_KEY

CSRFProtect enables CSRF protection; SECRET_KEY is needed for security tokens.

5fill in blank

hard

Fill all three blanks to safely handle user input in a Flask route.

Flask

from flask import request, escape

@app.route('/submit', methods=['POST'])
def submit():
    user_input = request.[1].get('[2]')
    safe_input = [3](user_input)
    return f'You entered: {safe_input}'

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

Aform

Bargs

Cescape

Dusername

Attempts:

3 left

💡 Hint

Common Mistakes

Using request.args for POST data

Not escaping user input

Use request.form to get POST data, 'username' as the input name, and escape() to prevent injection.

Practice

1. Why is security critical in a Flask web application?

easy

A. To protect user data and prevent unauthorized access

B. To make the app load faster

C. To add more colors to the website

D. To increase the number of pages

Solution

1. Step 1: Understand the purpose of security in web apps

   Security is meant to keep user data safe and stop unauthorized users from accessing sensitive parts of the app.

2. Step 2: Identify the correct reason among options

   Only To protect user data and prevent unauthorized access talks about protecting data and access, which matches the purpose of security.

3. Final Answer:

   To protect user data and prevent unauthorized access -> Option A

4. Quick Check:

   Security = Protect data and access [OK]

Hint: Security means protecting data and access [OK]

Common Mistakes:

• Confusing security with performance improvements
• Thinking security adds visual features
• Believing security increases page count

2. Which Flask function is used to stop a request and return an error code for unauthorized access?

easy

A. redirect()

B. abort()

C. render_template()

D. url_for()

Solution

1. Step 1: Recall Flask functions for handling errors

   Flask's abort() function immediately stops processing and returns an HTTP error code, useful for unauthorized access.

2. Step 2: Match the function to the purpose

   Only abort() fits the need to stop a request with an error code.

3. Final Answer:

   abort() -> Option B

4. Quick Check:

   abort() stops request with error [OK]

Hint: Use abort() to stop and send error code [OK]

Common Mistakes:

• Confusing abort() with redirect()
• Using render_template() to handle errors
• Thinking url_for() controls access

3. What will happen if this Flask route is accessed without a logged-in user?

from flask import abort, session, Flask
app = Flask(__name__)

@app.route('/dashboard')
def dashboard():
    if not session.get('user'):
        abort(401)
    return 'Welcome to your dashboard'

medium

A. The server returns a 401 Unauthorized error

B. The user sees 'Welcome to your dashboard'

C. The server crashes with an exception

D. The user is redirected to the login page

Solution

1. Step 1: Analyze the session check in the route

   The code checks if 'user' is in the session. If not, it calls abort(401), which sends a 401 Unauthorized error.

2. Step 2: Determine the response when no user is logged in

   Since no user is logged in, the condition is true and the abort triggers the 401 error response.

3. Final Answer:

   The server returns a 401 Unauthorized error -> Option A

4. Quick Check:

   abort(401) = 401 error response [OK]

Hint: abort(401) sends unauthorized error [OK]

Common Mistakes:

• Assuming the user sees the dashboard anyway
• Thinking abort crashes the server
• Confusing abort with redirect

4. Identify the security issue in this Flask route and how to fix it:

@app.route('/profile')
def profile():
    user_id = request.args.get('user_id')
    user = get_user_from_db(user_id)
    return f'Profile page of {user.name}'

medium

A. Return JSON instead of string

B. No issue, code is secure

C. Use POST method instead of GET

D. Missing user authentication check; add session check before fetching user

Solution

1. Step 1: Identify missing authentication

   The route fetches user data based on a URL parameter without checking if the requester is logged in or authorized.

2. Step 2: Fix by adding session user check

   Adding a check like if not session.get('user'): with abort(401) prevents unauthorized access.

3. Final Answer:

   Missing user authentication check; add session check before fetching user -> Option D

4. Quick Check:

   Check session before data access [OK]

Hint: Always check session before accessing user data [OK]

Common Mistakes:

• Thinking GET vs POST fixes security here
• Ignoring authentication checks
• Believing JSON return fixes security

5. You want to secure a Flask route so only logged-in users can access it. Which approach correctly combines Flask tools to achieve this?

@app.route('/settings')
def settings():
    # What should be added here?
    return 'User settings page'

hard

A. Redirect to homepage without checking session

B. Always return the page without checks

C. Check if 'user' in session; if not, abort(401); else return page

D. Use print() to log user info but no access control

Solution

1. Step 1: Understand access control with Flask session

   To secure a route, check if the user is logged in by verifying if 'user' exists in the session.

2. Step 2: Use abort(401) to block unauthorized users

   If the user is not logged in, call abort(401) to stop access and send an error.

3. Step 3: Return the page only if user is authenticated

   Only after passing the check should the page content be returned.

4. Final Answer:

   Check if 'user' in session; if not, abort(401); else return page -> Option C

5. Quick Check:

   Session check + abort(401) = secure route [OK]

Hint: Check session user, abort if missing, then return page [OK]

Common Mistakes:

• Skipping session check
• Using print() instead of access control
• Redirecting without verifying login