Session security in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does Flask's session cookie 'secure' flag do?

In Flask, setting the 'secure' flag on session cookies means:

A The cookie expires immediately after the browser closes.

B The cookie is encrypted with a secret key.

C The cookie is only sent over HTTPS connections.

D The cookie is accessible only via JavaScript.

💡 Hint

Think about when cookies are sent over the network.

The 'secure' flag ensures cookies are sent only over HTTPS, protecting them from being sent over unencrypted connections.

❓ component_behavior

intermediate

What happens if Flask's session cookie has 'httponly' set to false?

Consider this Flask configuration:
app.config['SESSION_COOKIE_HTTPONLY'] = false
What is the effect on session security?

A JavaScript can access the session cookie, increasing risk of XSS attacks.

B The session cookie expires immediately.

C The session cookie is only sent over HTTPS.

D The session cookie is encrypted automatically.

💡 Hint

Think about what 'httponly' controls.

Setting 'httponly' to false allows JavaScript to read the cookie, which can expose it to cross-site scripting (XSS) attacks.

❓ state_output

advanced

What is the output of this Flask session code snippet?

Given the Flask route below, what will be the value of session.get('count') after three requests?

from flask import Flask, session
app = Flask(__name__)
app.secret_key = 'secret'

@app.route('/')
def index():
    session['count'] = session.get('count', 0) + 1
    return str(session['count'])

A 1 on first request, 2 on second, 3 on third

B Always 1 on every request

C Raises a KeyError on first request

D 0 on first request, then 1, then 2

💡 Hint

Sessions store data between requests.

The code increments 'count' in the session each time the route is accessed, so it increases by 1 on each request.

📝 Syntax

advanced

Which Flask session configuration line correctly sets the cookie to expire in 1 hour?

Choose the correct way to set Flask session cookie expiration to 3600 seconds.

A app.config['PERMANENT_SESSION_LIFETIME'] = 3600

B app.config['SESSION_COOKIE_DURATION'] = 3600

C app.config['SESSION_COOKIE_EXPIRE'] = 3600

D app.config['PERMANENT_SESSION_LIFETIME'] = timedelta(seconds=3600)

💡 Hint

Check the type expected for 'PERMANENT_SESSION_LIFETIME'.

Flask expects a timedelta object for 'PERMANENT_SESSION_LIFETIME', not an integer.

🔧 Debug

expert

Why does this Flask app fail to keep session data between requests?

Examine this Flask app snippet:

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

@app.route('/')
def index():
    session['user'] = 'Alice'
    return 'Set user'

After refreshing the page multiple times, session.get('user') is always null. What is the cause?

A The session cookie is set to secure but the app runs on HTTP.

B The app is missing a secret key, so sessions cannot be signed.

C The session data is cleared explicitly after each request.

D The route does not return the session data.

💡 Hint

Flask sessions require a secret key to work properly.

Without app.secret_key, Flask cannot sign session cookies, so session data is lost between requests.

Practice

1. What is the main purpose of setting a SECRET_KEY in a Flask application for session security?

easy

A. To store user passwords securely

B. To encrypt the entire website content

C. To sign session cookies and prevent tampering

D. To speed up the server response time

Solution

1. Step 1: Understand the role of SECRET_KEY in Flask

   The SECRET_KEY is used to cryptographically sign session cookies, ensuring they are not altered by clients.

2. Step 2: Differentiate from other security tasks

   It does not encrypt website content or store passwords; its main role is to protect session integrity.

3. Final Answer:

   To sign session cookies and prevent tampering -> Option C

4. Quick Check:

   SECRET_KEY signs sessions = A [OK]

Hint: SECRET_KEY signs session cookies to prevent tampering [OK]

Common Mistakes:

• Thinking SECRET_KEY encrypts all data
• Confusing SECRET_KEY with password storage
• Assuming SECRET_KEY improves speed

2. Which of the following is the correct way to set a secret key in a Flask app for session security?

easy

A. app.set_secret('mysecret')

B. app.secret_key = 'mysecret'

C. app.SECRET = 'mysecret'

D. app.session_key = 'mysecret'

Solution

1. Step 1: Recall Flask's secret key attribute

   Flask uses app.secret_key to set the secret key for signing sessions.

2. Step 2: Verify syntax correctness

   Options A, C, and D use incorrect attribute names or methods not defined in Flask.

3. Final Answer:

   app.secret_key = 'mysecret' -> Option B

4. Quick Check:

   Use app.secret_key to set secret key = B [OK]

Hint: Use app.secret_key to set secret key in Flask [OK]

Common Mistakes:

• Using wrong attribute names like SECRET or session_key
• Trying to call a non-existent method set_secret
• Confusing uppercase and lowercase attribute names

3. Consider this Flask code snippet:

from flask import Flask, session
app = Flask(__name__)
app.secret_key = 'safe123'

@app.route('/')
def index():
    session['user'] = 'alice'
    return session.get('user')

What will the browser display when visiting the root URL?

medium

A. Error: secret key missing

B. null

C. session

D. alice

Solution

1. Step 1: Analyze session assignment

   The code sets session['user'] = 'alice', storing 'alice' in the session.

2. Step 2: Check session retrieval and return

   The function returns session.get('user'), which retrieves 'alice' from the session.

3. Final Answer:

   alice -> Option D

4. Quick Check:

   Session stores 'alice' and returns it = A [OK]

Hint: Session stores 'user' as 'alice', so output is 'alice' [OK]

Common Mistakes:

• Assuming session returns null if not set before
• Forgetting to set secret_key causes error but here it's set
• Confusing session object with string 'session'

4. What is wrong with this Flask session security setup?

from flask import Flask, session
app = Flask(__name__)
app.secret_key = ''  # empty string

@app.route('/')
def home():
    session['logged_in'] = True
    return 'Welcome'

medium

A. Empty secret_key means sessions are not securely signed

B. Missing import of session from flask

C. Route decorator syntax is incorrect

D. Session variable name 'logged_in' is invalid

Solution

1. Step 1: Check secret_key value

   The secret_key is set to an empty string, which is insecure and disables proper signing of session cookies.

2. Step 2: Validate other code parts

   Imports and route syntax are correct; session variable names can be any string.

3. Final Answer:

   Empty secret_key means sessions are not securely signed -> Option A

4. Quick Check:

   Empty secret_key disables secure session signing = C [OK]

Hint: Never use empty string as secret_key for session security [OK]

Common Mistakes:

• Ignoring empty secret_key security risk
• Thinking session variable names must follow strict rules
• Assuming route decorator syntax is wrong here

5. You want to improve session security in your Flask app by ensuring cookies are only sent over HTTPS and not accessible by JavaScript. Which configuration should you add?

hard

A. app.config.update({'SESSION_COOKIE_SECURE': true, 'SESSION_COOKIE_HTTPONLY': true})

B. app.config.update({'SESSION_COOKIE_SECURE': false, 'SESSION_COOKIE_HTTPONLY': false})

C. app.config.update({'SESSION_COOKIE_SAMESITE': 'null'})

D. app.config.update({'SESSION_COOKIE_DOMAIN': 'localhost'})

Solution

1. Step 1: Understand cookie security flags

   SESSION_COOKIE_SECURE=true ensures cookies are sent only over HTTPS, and SESSION_COOKIE_HTTPONLY=true prevents JavaScript access.

2. Step 2: Evaluate other options

   A sets domain but not security flags, B disables security flags, C changes SameSite but not HTTPS or HttpOnly.

3. Final Answer:

   app.config.update({'SESSION_COOKIE_SECURE': true, 'SESSION_COOKIE_HTTPONLY': true}) -> Option A

4. Quick Check:

   Secure and HttpOnly cookies = D [OK]

Hint: Set SESSION_COOKIE_SECURE and SESSION_COOKIE_HTTPONLY to true [OK]

Common Mistakes:

• Setting SESSION_COOKIE_SECURE to false
• Confusing SameSite with Secure and HttpOnly flags
• Not setting HttpOnly to prevent JavaScript access