Session security in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of session security in Flask?

Session security helps protect user data stored in sessions from being stolen or tampered with during a web session.

beginner

How does Flask protect session data by default?

Flask signs session cookies with a secret key to prevent tampering, ensuring the data cannot be changed by the client.

beginner

Why should you set the 'SECRET_KEY' in a Flask app?

The 'SECRET_KEY' is used to sign session cookies. Without it, Flask cannot secure session data, making it vulnerable to attacks.

intermediate

What is the role of 'secure' and 'httponly' flags in Flask session cookies?

'secure' ensures cookies are sent only over HTTPS, and 'httponly' prevents JavaScript from accessing cookies, reducing risk of theft.

intermediate

How can you prevent session fixation attacks in Flask?

Regenerate the session ID after login by clearing the session or using Flask extensions to assign a new session cookie.

What does Flask use to protect session cookies from tampering?

A No protection by default

B Encryption of cookies by default

C Storing sessions only on the server

D A secret key to sign cookies

Flask signs session cookies with a secret key to detect tampering but does not encrypt them by default.

Which flag should be set to ensure cookies are sent only over HTTPS?

A samesite

B httponly

C secure

D domain

The 'secure' flag tells the browser to send cookies only over HTTPS connections.

What is the risk if 'httponly' flag is not set on session cookies?

A Cookies can be read by JavaScript, increasing risk of theft

B Cookies will not be sent to the server

C Cookies will expire immediately

D Cookies will be encrypted

'httponly' prevents JavaScript access to cookies, protecting against cross-site scripting attacks stealing cookies.

How can you improve session security after a user logs in?

A Keep the same session ID

B Regenerate the session ID

C Disable cookies

D Store session data in local storage

Regenerating the session ID after login helps prevent session fixation attacks.

What must you set in your Flask app to enable session signing?

A SECRET_KEY

B SESSION_COOKIE_NAME

C DEBUG

D SESSION_TYPE

The 'SECRET_KEY' is required for Flask to sign session cookies and protect them from tampering.

Explain how Flask secures session data and what settings you should configure to enhance session security.

Think about cookie protection and session management best practices.

Describe common session security risks in web apps and how Flask helps mitigate them.

Consider what attackers try to do with sessions and how Flask defends.

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