Cross Site Request Forgery protection weak to packet sniffing

Your website is vulnerable because the CSRF_COOKIE_SECURE setting is not set - so hackers have an easier time stealing your CSRF cookies on HTTP connections, allowing them to circumvent your CSRF protection.

CsrfMiddleware marks the CSRF cookie as secure when CSRF_COOKIE_SECURE = True, to make the browser only send cookie over secure HTTPS connection.

Cookies sent over insecure HTTP are unencrypted, so hackers can steal the CSRF cookie using a packet sniffer - allowing them to use it to trick the browser into thinking a request on their website was performed on your website by the logged a user.-.

If we spot this issue in your GitHub pull request we give this advice:

settings.pysecurityhigh
+
from ast import literal_eval
+
from os import getenv
+
MIDDLEWARE = [
    'django.middleware.csrf.CsrfViewMiddleware',
    ...
]
+
+
# feature flagged so can turn off in local development
+
CSRF_COOKIE_SECURE = literal_eval(getenv("HTTPS_ONLY", "True"))

Your website is vulnerable because the CSRF_COOKIE_SECURE setting is not set - so hackers have an easier time stealing your CSRF cookies on HTTP connections, allowing them to circumvent your CSRF protection.

Read more
Protect your pull requests from over 40 types of common Django technical debts with our GitHub code review bot.

Configuring this check

Django Doctor will run this check by default. No configuration is needed but the check can be turned on/off using check code missing-csrf-secure in your pyproject.toml file.

Read more about configuring Django Doctor.